Loading...
Loading...
Found 191 Skills
Quick guide to choosing the right creative writing skill. Use when you need help deciding which creative writing skill to use for a specific task - brainstorming vs documentation, critique vs writing, etc.
Use this skill when the user needs help with personal writing — either starting a new piece from scratch (inspiration/brainstorming) or reviewing and polishing an existing article (proofreading/editing). Invoke immediately when: the user shares an article and asks for feedback, wants to improve their writing style, feels stuck on what to write, wants help structuring a travel piece/TIL note/personal essay, or asks to review Chinese writing quality. Trigger phrases: 帮我改文章, 检查一下, 润色, 校对, 不知道写什么, 帮我构思, 写游记, 记录 TIL, 写点什么. NOT for diary writing (use diary-assistant) or formal business communications.
Write a plan file for a multi-step task (Step 3 of /task). Runs one brainstorming round then writes ai-workspace/plans/<name>.md from TEMPLATE.md. Skipped for one-sentence scope. Does NOT review — that is /review (Step 4).
Orchestrates design workflows by routing work through brainstorming, multi-agent review, and execution readiness in the correct order. Prevents premature implementation, skipped validation, and unreviewed high-risk designs.
Plan Plus — Brainstorming-Enhanced PDCA Planning. Combines intent discovery from brainstorming methodology with bkit PDCA's structured planning. Produces higher-quality Plan documents by exploring user intent, comparing alternatives, and applying YAGNI review before document generation. Use proactively when user mentions planning with brainstorming, intent discovery, exploring alternatives, or wants a more thorough planning process. Triggers: plan-plus, plan plus, brainstorming plan, enhanced plan, deep plan, 플랜 플러스, 브레인스토밍, 기획, 의도 탐색, 대안 탐색, プランプラス, ブレインストーミング, 企画, 意図探索, 计划加强, 头脑风暴, 深度规划, 意图探索, plan mejorado, lluvia de ideas, planificación profunda, plan amélioré, remue-méninges, planification approfondie, erweiterter Plan, Brainstorming, vertiefte Planung, piano migliorato, brainstorming, pianificazione approfondita Do NOT use for: simple tasks that don't need planning, code-only changes.
Generate a complete conference proposal through a structured brainstorming Q&A. Produces abstract, extended abstract, title variants, and learning outcomes — calibrated to the session format and grounded in your DevRel context.
Comet Phase 2: In-depth Design. Invoke with /comet-design. Produce Design Doc and delta spec through brainstorming.
Use when brainstorming, evaluating architecture choices, or comparing trade-offs where independent perspectives from different model families (Claude/Codex/Gemini) would surface blind spots
Brainstorm product ideas for an existing product using multi-perspective ideation from PM, Designer, and Engineer viewpoints. Use when generating new feature ideas, brainstorming solutions for an identified opportunity, or ideating with a product trio.
Use when the user wants to use Google Gemini for analysis, large files or codebases, sandbox execution, or brainstorming. Uses headless Gemini CLI scripts (no MCP). Triggers on "use Gemini", "analyze with Gemini", "large file", "sandbox", "brainstorm with Gemini".
Personalized brainstorming agent that generates sellable utility ideas (CLI, TUI, GUI, agent tools) tailored to the user's stack and niche, with persistent memory of past suggestions. Triggered by: /spark.
YC Office Hours — two modes. Startup mode: six forcing questions that expose demand reality, status quo, desperate specificity, narrowest wedge, observation, and future-fit. Builder mode: design thinking brainstorming for side projects, hackathons, learning, and open source. Saves a design doc. Use when asked to "brainstorm this", "I have an idea", "help me think through this", "office hours", or "is this worth building". Proactively suggest when the user describes a new product idea or is exploring whether something is worth building — before any code is written. Use before /plan-ceo-review or /plan-eng-review.