Back to Details

brainstorm

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Brainstorm

头脑风暴

Overview

概述

Use this skill to convert rough ideas into clear, reviewable design outputs through structured dialogue.
The goal is to:
  1. Clarify requirements and constraints
  2. Explore alternatives with trade-offs
  3. Produce a concrete, validated design brief in 
    docs/brainstorms/...
  4. Hand off cleanly to 
    write-plan
    when the user is ready
This skill is for exploration and specification only. Do not implement code changes.
使用本技能通过结构化对话将粗略想法转化为清晰、可评审的设计产出。
目标是：
  1. 明确需求与约束条件
  2. 探索带有取舍的多种备选方案
  3. 在
    docs/brainstorms/...
    路径下生成具体的、经过验证的设计简报
  4. 当用户准备就绪时，顺畅交接至
    write-plan
    技能
本技能仅用于探索与规格定义，请勿进行代码变更。

Workflow

工作流程

Step 1: Gather Project Context

步骤1：收集项目背景信息

Before asking design questions, inspect enough project context to avoid proposing incompatible solutions.
  • Review 
    docs/
    first, especially: 
    • docs/project-pdr.md
    • docs/architecture.md
    • docs/codebase.md
    • docs/code-standard.md
  • Check key implementation files relevant to the idea
  • Note constraints from existing architecture, dependencies, and conventions
Keep this pass focused. Only gather what is needed for the current idea.
在提出设计问题前，需充分了解项目背景，避免提出不兼容的解决方案。
  • 先查看
    docs/
    目录下的内容，尤其是： 
    • docs/project-pdr.md
    • docs/architecture.md
    • docs/codebase.md
    • docs/code-standard.md
  • 检查与当前想法相关的关键实现文件
  • 记录现有架构、依赖项和约定带来的约束条件
此阶段需聚焦核心，仅收集与当前想法相关的必要信息。

Step 2: Clarify Requirements (One Question at a Time)

步骤2：逐步明确需求（一次一个问题）

Ask targeted questions sequentially to remove ambiguity.
  • Ask exactly one question per message
  • Prefer multiple-choice options when practical
  • Use open-ended questions only when necessary
  • Focus on:
    • Objective and user value
    • Scope boundaries
    • Constraints (technical, UX, performance, timeline)
    • Success criteria
    • Non-goals
Do not jump to implementation details too early.
通过针对性的连续提问消除歧义。
  • 每条消息仅提出一个问题
  • 实际可行时优先使用选择题形式
  • 仅在必要时使用开放式问题
  • 聚焦以下方面：
    • 目标与用户价值
    • 范围边界
    • 约束条件（技术、UX、性能、时间线）
    • 成功标准
    • 非目标
请勿过早跳转至实现细节。

Step 3: Explore Approaches

步骤3：探索备选方案

Propose 2-3 viable approaches.
For each approach, include:
  • Short summary
  • Pros
  • Cons / risks
  • Complexity estimate
  • Recommended use conditions
Lead with your recommended option and explain why it best fits the project context and constraints.
提出2-3种可行方案。
每个方案需包含：
  • 简短概述
  • 优势
  • 劣势/风险
  • 复杂度预估
  • 推荐适用场景
优先展示你推荐的方案，并说明其为何最符合项目背景与约束条件。

Step 4: Present the Design Incrementally

步骤4：逐步呈现设计内容

Once requirements are clear, present the design in small sections (about 200-300 words each), validating after each section.
Suggested section order:
  1. Problem framing and goals
  2. Proposed architecture / flow
  3. Data model and interfaces
  4. Error handling and edge cases
  5. Testing and verification strategy
  6. Rollout considerations (if applicable)
After each section, ask whether to proceed or adjust.
需求明确后，分小部分呈现设计内容（每部分约200-300字），每部分后进行验证。
建议的内容顺序：
  1. 问题框架与目标
  2. 拟议架构/流程
  3. 数据模型与接口
  4. 错误处理与边缘情况
  5. 测试与验证策略
  6. 上线考量（如适用）
每部分内容展示后，询问用户是否继续或调整。

Step 5: Write Brainstorm Artifacts

步骤5：撰写头脑风暴成果文档

Persist results to the standardized location:
  • Directory: 
    docs/brainstorms/YYMMDD-HHmm-<topic-slug>/
  • Main file (required): 
    docs/brainstorms/YYMMDD-HHmm-<topic-slug>/SUMMARY.md
  • Optional supporting files: 
    • docs/brainstorms/YYMMDD-HHmm-<topic-slug>/section-01-<slug>.md
    • docs/brainstorms/YYMMDD-HHmm-<topic-slug>/section-02-<slug>.md
    • etc.
SUMMARY.md
should contain:
  • Title
  • Created timestamp
  • Context
  • Goals / non-goals
  • Chosen approach and rationale
  • Alternatives considered
  • Risks and mitigations
  • Open questions
  • Next step recommendation
将结果保存至标准化路径：
  • 目录：
    docs/brainstorms/YYMMDD-HHmm-<topic-slug>/
  • 主文件（必填）：
    docs/brainstorms/YYMMDD-HHmm-<topic-slug>/SUMMARY.md
  • 可选支持文件： 
    • docs/brainstorms/YYMMDD-HHmm-<topic-slug>/section-01-<slug>.md
    • docs/brainstorms/YYMMDD-HHmm-<topic-slug>/section-02-<slug>.md
    • 等等
SUMMARY.md
应包含：
  • 标题
  • 创建时间戳
  • 背景信息
  • 目标/非目标
  • 选定方案及理由
  • 已考量的备选方案
  • 风险与缓解措施
  • 待解决问题
  • 下一步建议

Step 6: Close the Loop

步骤6：闭环收尾

After writing artifacts:
  1. Ask the user to review and provide feedback
  2. If feedback exists, revise artifacts
  3. If no feedback, ask whether to proceed to planning
  4. If approved, hand off to 
    write-plan
    using the brainstorm output as source context
完成文档撰写后：
  1. 请用户审阅并提供反馈
  2. 若有反馈，修订文档
  3. 若无反馈，询问是否进入规划阶段
  4. 若获批准，以头脑风暴输出内容为上下文，交接至
    write-plan
    技能

Rules

规则

  • Do not write production code or make implementation changes in this skill
  • Keep interaction lightweight and iterative
  • Prefer clarity over completeness when uncertain; ask a follow-up question
  • Apply YAGNI: remove unnecessary features from proposals
  • Align all recommendations with project documentation and standards
  • Keep assumptions explicit; do not guess silently
  • 请勿在本技能中编写生产代码或进行实现变更
  • 保持交互轻量化、迭代式推进
  • 当存在不确定性时，优先保证清晰性而非完整性；提出跟进问题
  • 应用YAGNI原则：从提案中移除不必要的功能
  • 所有建议需与项目文档和标准保持一致
  • 明确列出假设条件；请勿自行猜测

Output Quality Checklist

输出质量检查清单

Before finalizing 
SUMMARY.md
, confirm:
  • Requirements are explicit and testable
  • Scope and non-goals are clear
  • Recommended approach is justified with trade-offs
  • Risks and unknowns are documented
  • Handoff to planning is actionable
最终确定
SUMMARY.md
前，确认：
  • 需求明确且可测试
  • 范围与非目标清晰
  • 推荐方案有取舍分析作为支撑
  • 风险与未知项已记录
  • 向规划阶段的交接可落地

Integration

集成

  • Use 
    scripts/get-time.sh
    to generate: 
    • YYMMDD-HHmm
      for folder naming
    • YYYY-MM-DD HH:mm:ss
      for document timestamps
  • Next workflow step: 
    write-plan
  • 使用
    scripts/get-time.sh
    生成：
    • 用于文件夹命名的
      YYMMDD-HHmm
    • 用于文档时间戳的
      YYYY-MM-DD HH:mm:ss
  • 下一个工作流步骤：
    write-plan