spec-brainstorm
通过协作对话明确 WHAT，形成右尺寸 requirements 文档。
基本信息
| 字段 | 内容 |
|---|---|
| Skill | spec-brainstorm |
| 类型 | workflow command |
| 研发链路位置 | Spec |
| 入口 | /spec:brainstorm / $spec-brainstorm |
| Source | skills/spec-brainstorm/SKILL.md |
描述
Explore requirements and approaches through collaborative dialogue before writing a right-sized requirements document and planning implementation. Use for feature ideas, problem framing, when the user says ''let''s brainstorm'', or when they want to think through options before deciding what to build. Also use when a user describes a vague or ambitious feature request, asks ''what should we build'', ''help me think through X'', presents a problem with multiple valid solutions, or seems unsure about scope or direction — even if they don''t explicitly ask to brainstorm.
何时使用
- 用户还在定义问题或范围。
- 存在多个合理产品方向。
- 需要先整理 actors、flows、acceptance examples 和 non-goals。
工作步骤
- 读取用户意图、代码库背景、已有 requirements、历史学习和外部证据。
- 收敛问题框架、用户流、边界、验收标准或候选方向。
- 区分必须现在解决的问题和可延后到计划或实现阶段的问题。
- 把 WHAT 层证据交给 plan 或 doc-review。
输出
- requirements、ideation artifact、scope boundaries 或 open questions。
- 可供计划阶段追溯的 actors、flows、acceptance examples 和关键决策。
Agent 调度
- 可按需要引入 spec-flow、product、design、security、repo、web 或 issue research agents。
- agent 产出是证据和问题发现，最终需求边界仍由当前 workflow 汇总。
边界
- 不写实现计划。
- 当 HOW 已清楚且可执行时应进入 spec-plan 或 spec-work。