Back to Details

brainstorm

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

/brainstorm — Clarify Goals Before Planning

/brainstorm — 规划前明确目标

Purpose: Separate WHAT from HOW. Explore the problem space before committing to a solution.
Four phases:
  1. Assess clarity — Is the goal specific enough?
  2. Understand idea — What problem, who benefits, what exists?
  3. Explore approaches — Generate options, compare tradeoffs
  4. Capture design — Write structured output for 
    /plan
目的： 区分目标（WHAT）与实现方式（HOW）。在确定解决方案前先探索问题领域。
四个阶段：
  1. 评估清晰度 — 目标是否足够具体？
  2. 理解需求 — 要解决什么问题？受益方是谁？现有方案是什么？
  3. 探索实现路径 — 生成备选方案，比较利弊
  4. 记录设计 — 为
    /plan
    生成结构化输出

Quick Start

快速开始

bash
/brainstorm "add user authentication"     # full 4-phase process
/brainstorm                                # prompts for goal
bash
/brainstorm "add user authentication"     # 完整的四阶段流程
/brainstorm                                # 提示输入目标

Execution Steps

执行步骤

Phase 1: Assess Clarity

阶段1：评估清晰度

If the user provided a goal string, evaluate it. Otherwise prompt for one.
Use 
AskUserQuestion
with options to gauge clarity:
  • clear — Goal is specific and actionable (e.g., "add JWT auth to the API")
  • vague — Goal exists but needs narrowing (e.g., "improve security")
  • exploring — No firm goal yet, just a direction (e.g., "something with auth")
If vague or exploring, ask follow-up questions to sharpen the goal before proceeding. Do NOT move to Phase 2 until you have a concrete problem statement (one sentence, testable).
如果用户提供了目标字符串，先对其进行评估。否则提示用户输入目标。
使用
AskUserQuestion
工具并提供选项来评估清晰度：
  • 清晰 — 目标具体且可执行（例如："为API添加JWT认证"）
  • 模糊 — 有目标但需要细化（例如："提升安全性"）
  • 探索中 — 尚未确定明确目标，只有大致方向（例如："和认证相关的功能"）
如果目标模糊或处于探索中，在进入阶段2前，先通过后续问题来明确目标。在得到具体的问题陈述（一句话、可验证）之前，不要进入阶段2。

Phase 2: Understand the Idea

阶段2：理解需求

Answer these questions (use codebase exploration as needed):
  1. What problem does this solve? — State the pain point in concrete terms.
  2. Who benefits? — End users, developers, operators, CI pipeline?
  3. What exists today? — Current state, prior art in the codebase, adjacent systems.
  4. What constraints matter? — Performance, compatibility, security, timeline.
Summarize findings before moving on. If anything is unclear, ask the user.
回答以下问题（必要时可探索代码库）：
  1. 要解决什么问题？ — 用具体语言描述痛点。
  2. 受益方是谁？ — 终端用户、开发人员、运维人员、CI流水线？
  3. 现有方案是什么？ — 当前状态、代码库中的已有实现、相关系统。
  4. 有哪些约束条件？ — 性能、兼容性、安全性、时间周期。
在进入下一阶段前总结发现的信息。如果有不明确的地方，询问用户。

Phase 3: Explore Approaches

阶段3：探索实现路径

Generate 2-3 distinct approaches. For each:
  • Name — Short label (e.g., "JWT middleware", "OAuth proxy", "Session cookies")
  • How it works — 2-3 sentences
  • Pros — What it gets right
  • Cons — What it gets wrong or defers
  • Effort — Rough scope (small / medium / large)
Present the comparison and use 
AskUserQuestion
to let the user pick an approach or request a hybrid.
生成2-3种不同的实现方案。针对每个方案：
  • 名称 — 简短标签（例如："JWT中间件"、"OAuth代理"、"会话Cookie"）
  • 工作原理 — 2-3句话说明
  • 优势 — 方案的优点
  • 劣势 — 方案的不足或待解决的问题
  • 工作量 — 大致范围（小 / 中 / 大）
展示方案对比，并用
AskUserQuestion
让用户选择一个方案或要求混合方案。

Phase 4: Capture Design

阶段4：记录设计

Generate a date slug: 
YYYY-MM-DD-<goal-slug>
(lowercase, hyphens, no spaces).
Write the output file to 
.agents/brainstorm/YYYY-MM-DD-<slug>.md
:
markdown
---
name: <goal-slug>
date: YYYY-MM-DD
status: captured
---
生成日期格式的文件名后缀：
YYYY-MM-DD-<goal-slug>
（小写、连字符连接、无空格）。
将输出文件写入
.agents/brainstorm/YYYY-MM-DD-<slug>.md
：
markdown
---
name: <goal-slug>
date: YYYY-MM-DD
status: captured
---

Brainstorm: <Goal>

Brainstorm: <Goal>

Problem Statement

Problem Statement

Approaches Considered

Approaches Considered

Selected Approach

Selected Approach

Open Questions

Open Questions

Next Step: /plan

Next Step: /plan


All five sections must be populated. The "Next Step" section should contain a concrete `/plan` invocation suggestion with the selected approach as context.

Create the `.agents/brainstorm/` directory if it does not exist.

---

必须填充所有五个部分。"下一步"部分应包含具体的`/plan`调用建议，并以选定的方案为上下文。

如果`.agents/brainstorm/`目录不存在，先创建该目录。

---

Termination

终止条件

Phase 4 output written = done. No further phases, no loops.
完成阶段4的输出文件写入即结束流程。无后续阶段，无循环。

Validation

验证

After writing the output file, verify:
  1. File exists at the expected path
  2. All 5 sections (
    Problem Statement
    , 
    Approaches Considered
    , 
    Selected Approach
    , 
    Open Questions
    , 
    Next Step: /plan
    ) are present and non-empty
Report the file path to the user.
写入输出文件后，验证以下内容：
  1. 文件存在于预期路径
  2. 所有5个部分（
    Problem Statement
    、
    Approaches Considered
    、
    Selected Approach
    、
    Open Questions
    、
    Next Step: /plan
    ）均已存在且非空
向用户报告文件路径。

Examples

示例

Example 1: Specific goal
User: /brainstorm "add rate limiting to the API"

Phase 1: Goal is clear — add rate limiting to the API.
Phase 2: Problem is uncontrolled request volume causing timeouts.
         Benefits operators and end users. No rate limiting exists today.
Phase 3: Three approaches — token bucket middleware, API gateway,
         per-route decorators. User picks token bucket.
Phase 4: Writes .agents/brainstorm/2026-02-17-rate-limiting.md
Example 2: Vague goal
User: /brainstorm "improve performance"

Phase 1: Goal is vague. Asks: "Which part? API response times,
         build speed, database queries, or something else?"
         User says: "API response times on the search endpoint."
Phase 2: Investigates search endpoint, finds N+1 queries.
Phase 3: Approaches — query optimization, caching layer, pagination.
Phase 4: Writes .agents/brainstorm/2026-02-17-search-performance.md
示例1：具体目标
User: /brainstorm "add rate limiting to the API"

阶段1：目标清晰 — 为API添加限流功能。
阶段2：问题是无控制的请求量导致超时。受益方是运维人员和终端用户。目前没有限流机制。
阶段3：三种方案 — 令牌桶中间件、API网关、路由装饰器。用户选择令牌桶方案。
阶段4：生成文件.agents/brainstorm/2026-02-17-rate-limiting.md
示例2：模糊目标
User: /brainstorm "improve performance"

阶段1：目标模糊。询问：“具体是哪部分？API响应时间、构建速度、数据库查询还是其他？”用户回答：“搜索接口的API响应时间。”
阶段2：调查搜索接口，发现N+1查询问题。
阶段3：方案 — 查询优化、缓存层、分页。
阶段4：生成文件.agents/brainstorm/2026-02-17-search-performance.md

See Also

相关链接

  • skills/plan/SKILL.md — Decompose the selected approach into actionable issues
  • skills/plan/SKILL.md — 将选定的方案分解为可执行的任务