Back to Details

brainstorm

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Brainstorm

头脑风暴

Use this skill to guide a user from a rough idea to a clear design/spec by asking targeted questions, one at a time, after first inspecting the project state.
当用户有一个初步想法，且你已先了解项目状态后，可使用该技能通过逐个提出针对性问题，引导用户从模糊想法形成清晰的设计/规范。

Workflow

工作流程

  1. Scan the project context
    • Review the working directory to understand the current state, constraints, and any existing docs or code.
    • Summarize what you saw in 2-4 sentences only if it helps frame the next question.
  2. Ask refining questions (one per message)
    • Ask exactly one question per response.
    • Prefer multiple-choice questions with 3-5 options; include an "Other: ____" option when helpful.
    • For multiple-choice questions, mark exactly one option as recommended so the user has a clear default.
    • In Codex 
      request_user_input
      , mark the recommended choice by suffixing the label with 
      (Recommended)
      . In Claude 
      AskUserQuestion
      , use an explicit 
      recommended
      flag when available or clearly label one option as recommended.
    • Use open-ended questions only when options would be misleading.
    • Sequence questions from highest-uncertainty to lowest-uncertainty.
    • Do not ask questions that can be trivially answered by inspecting the repo or using available tools; look it up first.
    • Keep each question tightly scoped and decision-oriented.
    • For Claude, ask questions via AskUserQuestion.
  3. Converge on understanding
    • Once the idea is clear enough to describe a design/spec, stop asking questions.
    • Explicitly indicate you are switching from questions to describing the design.
  4. Describe the design in sections
    • Provide the design/spec in sections of ~200-300 words each.
    • After each section, ask whether it looks right so far before continuing.
    • Incorporate feedback and revise the next section accordingly.
  5. Beads + planning handoff
    • After the final spec section is approved, summarize the spec into bead fields: title, description, design, acceptance.
    • Ask one multiple-choice question covering the next step (beads and/or plan), and mark one option as recommended. Example choices: create a single bead, create an epic + milestones, proceed to plan only, or pause.
    • If beads are requested and granularity is unclear, ask a single follow-up question to choose between a single bead vs an epic with milestone beads.
    • Decision rule for granularity:
      • Single bead: 1-3 sessions, cohesive flow, minimal handoffs.
      • Epic + milestones: longer work or clear checkpoints, even if sequential. Use linear dependencies if steps must be done in order.
    • If a plan is requested, provide a concise spec recap (goals, non-goals, UX, data/logic, constraints, acceptance) to seed the plan.
    • If a plan is created later, link it in the bead design field.
  1. 扫描项目上下文
    • 查看工作目录，了解当前项目状态、限制条件以及任何现有文档或代码。
    • 仅当有助于为下一个问题搭建框架时，用2-4句话总结你所了解到的内容。
  2. 提出细化问题（每条消息仅一个问题）
    • 每条回复仅提出一个问题。
    • 优先选择包含3-5个选项的选择题；必要时加入“其他：____”选项。
    • 对于选择题，需明确标记一个推荐选项，为用户提供清晰的默认选择。
    • 在Codex的
      request_user_input
      中，通过在标签后添加
      (Recommended)
      来标记推荐选项。在Claude的
      AskUserQuestion
      中，若有可用的显式
      recommended
      标记则使用该标记，或清晰标注一个选项为推荐项。
    • 仅当选项会产生误导时，才使用开放式问题。
    • 按照不确定性从高到低的顺序提出问题。
    • 不要提出可通过查看代码库或使用现有工具轻易回答的问题；先自行查找答案。
    • 每个问题需紧扣主题，以决策为导向。
    • 对于Claude，通过AskUserQuestion提出问题。
  3. 达成共识
    • 当想法足够清晰，能够描述设计/规范时，停止提问。
    • 明确告知用户你将从提问切换到描述设计。
  4. 分章节描述设计
    • 将设计/规范分为多个章节，每个章节约200-300字。
    • 每个章节描述完毕后，先询问用户当前内容是否正确，再继续下一章节。
    • 根据反馈调整并完善下一章节内容。
  5. Beads + 规划交接
    • 当最终规范章节获得认可后，将规范总结为beads字段：标题、描述、设计、验收标准。
    • 提出一个涵盖下一步（beads和/或规划）的选择题，并标记一个推荐选项。示例选项：创建单个bead、创建epic + 里程碑、仅进入规划阶段、或暂停。
    • 若用户要求创建beads但粒度不明确，可提出一个后续问题，让用户选择创建单个bead还是带里程碑beads的epic。
    • 粒度决策规则：
      • 单个bead：1-3个工作阶段，流程连贯，交接最少。
      • Epic + 里程碑：工作周期较长或有明确检查点，即使是顺序执行的工作。若步骤必须按顺序完成，使用线性依赖关系。
    • 若用户要求制定规划，先提供简洁的规范回顾（目标、非目标、用户体验、数据/逻辑、限制条件、验收标准）作为规划基础。
    • 若后续创建了规划，需在bead的设计字段中添加链接。

Style rules

风格规则

  • Ask only one question per message.
  • Keep momentum: no long preambles or multi-paragraph lead-ins.
  • Use concrete language and avoid filler.
  • Do not announce the skill or preface with meta statements like "Using the brainstorm skill because...".
  • When asking about beads/plan, use a single multiple-choice question; only follow up if bead granularity needs a choice.
  • For each multiple-choice question, ensure exactly one option is explicitly marked as recommended.
  • 每条消息仅提出一个问题。
  • 保持节奏：不要使用冗长的开场白或多段落的引入内容。
  • 使用具体语言，避免冗余。
  • 不要宣布正在使用该技能，也不要添加诸如“因为……所以使用头脑风暴技能”这类元陈述。
  • 当询问beads/规划相关问题时，使用单个选择题；仅当bead粒度需要选择时才进行后续提问。
  • 每个选择题必须明确标记一个推荐选项。