brainstorming-ideas

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Brainstorming Ideas Into Designs

将头脑风暴的想法转化为设计

Transform vague ideas into fully-formed designs through structured collaborative dialogue.

Use TodoWrite to track these 7 phases:

Understand the idea (dialogue first, no agents)
Explore requirements (Starbursting questions)
Checkpoint - offer exploration/research options
Research similar solutions (if requested)
Present approaches with recommendation
Validate design incrementally
Document and next steps

通过结构化的协作式对话，将模糊的想法转化为完整的设计方案。

使用TodoWrite 来跟踪以下7个阶段：

理解想法（先对话，不调用Agent）
探索需求（使用星爆式提问法）
检查点 - 提供探索/研究选项
研究同类解决方案（若用户要求）
呈现实现方案并给出推荐
逐步验证设计
文档记录与后续步骤

Core Principles

核心原则

Dialogue first - Ask the user before spawning any agents
One question at a time - Never batch multiple questions
Multiple choice preferred - Easier to answer than open-ended
"Other" always available - Free text input for custom responses
YAGNI ruthlessly - Challenge every feature's necessity
Incremental validation - Present design in 200-300 word sections
Agents on request - Only explore/research when user chooses it

先对话 - 在调用任何Agent前先询问用户
一次一个问题 - 绝不批量提出多个问题
优先选择题 - 比开放式问题更易回答
始终保留“其他”选项 - 支持自定义文本输入
严格遵循YAGNI原则 - 质疑每个功能的必要性
逐步验证 - 按200-300字的分段呈现设计
按需调用Agent - 仅在用户选择时进行探索/研究

Phase 1: Understand the Idea

阶段1：理解想法

Start with dialogue, not agents. Ask the user directly.

从对话开始，而非调用Agent。直接询问用户。

1a. Initial Question

1a. 初始问题

Use AskUserQuestion:

Header	Question	Options
Idea type	What would you like to brainstorm?	1. New feature - Add new functionality 2. Modification - Change existing behavior 3. Integration - Connect with external system 4. Exploration - Not sure yet, let's discover

使用AskUserQuestion工具：

标题	问题	选项
想法类型	你想要针对什么进行头脑风暴？	1. 新功能 - 添加全新功能 2. 功能修改 - 变更现有行为 3. 系统集成 - 与外部系统对接 4. 探索性讨论 - 还不确定，先一起梳理想法

1b. Follow-up (based on response)

1b. 跟进问题（基于用户回复）

Ask clarifying questions using AskUserQuestion. Keep it conversational:

"Can you describe this in a sentence or two?" (free text via "Other")
"What triggered this idea?" with context-appropriate options
"Is there an existing feature this builds on?"

使用AskUserQuestion工具提出澄清问题，保持对话式语气：

“能否用一两句话描述这个想法？”（通过“其他”选项支持自由文本输入）
“这个想法的触发原因是什么？”提供符合上下文的选项
“这个想法是否基于现有功能进行拓展？”

Phase 2: Explore Requirements (Starbursting)

阶段2：探索需求（星爆式提问法）

Ask questions one at a time using AskUserQuestion. Adapt based on idea type.

一次提出一个问题，使用AskUserQuestion工具，根据想法类型调整提问内容。

Question Framework (5WH)

问题框架（5WH）

Question Type	When to Ask	Example AskUserQuestion
WHO	Always first	"Who will use this?" → Options: Existing users, New segment, Internal, API consumers
WHY	After WHO	"What problem does this solve?" → Options based on detected pain points
WHAT	After WHY is clear	"What's the core capability?" → Open or options based on research
WHERE	For integrations/modifications	"Where should this live?" → Options based on codebase exploration
HOW	After approach research	"How should we implement?" → Present 2-3 technical approaches

问题类型	提问时机	示例AskUserQuestion设置
WHO	始终第一个提问	“谁会使用这个功能？” → 选项：现有用户、新用户群体、内部人员、API消费者
WHY	在WHO之后提问	“这个功能解决什么问题？” → 基于检测到的痛点提供选项
WHAT	在明确WHY之后提问	“核心能力是什么？” → 开放式提问或基于研究结果提供选项
WHERE	针对集成/修改类想法提问	“这个功能应该部署在哪里？” → 基于代码库探索结果提供选项
HOW	在方案研究之后提问	“我们应该如何实现？” → 呈现2-3种技术实现方案

Adaptive Questioning

自适应提问

Skip questions when answers are obvious from context
If user seems certain, move faster to approaches
If user seems uncertain, explore deeper with sub-questions
Use "Other" option to allow custom responses

当答案从上下文可明显看出时，跳过对应问题
如果用户态度明确，加快推进到方案阶段
如果用户态度不确定，通过子问题深入探索
使用“其他”选项支持自定义回复

Phase 3: Checkpoint - Gather More Context?

阶段3：检查点 - 是否需要收集更多上下文？

After understanding requirements, ask before spawning any agents:

Header	Question	Options
Next step	How should we proceed?	1. Explore codebase - Check existing patterns and tech stack 2. Research solutions - Look up how others solve this 3. Both - Explore then research 4. Skip to approaches - I know what I want

在理解需求后，调用任何Agent前先询问用户：

标题	问题	选项
下一步	我们应该如何推进？	1. 探索代码库 - 检查现有模式与技术栈 2. 研究解决方案 - 了解其他产品的实现方式 3. 两者都做 - 先探索再研究 4. 直接进入方案阶段 - 我清楚自己想要的方向

If user chooses "Explore codebase":

如果用户选择“探索代码库”：

Task(
  subagent_type="Explore",
  prompt="Quick scan: project structure, tech stack, patterns relevant to [user's idea]",
  run_in_background=false
)

Then summarize findings and ask: "Based on this, should we also research external solutions?"

Task(
  subagent_type="Explore",
  prompt="Quick scan: project structure, tech stack, patterns relevant to [user's idea]",
  run_in_background=false
)

然后总结探索结果并询问：“基于以上结果，我们是否还需要研究外部解决方案？”

If user chooses "Research solutions":

如果用户选择“研究解决方案”：

Proceed to Phase 4.

进入阶段4。

If user chooses "Skip to approaches":

如果用户选择“直接进入方案阶段”：

Jump directly to Phase 5 (Present Approaches).

直接跳转到阶段5（呈现实现方案）。

Phase 4: Research Similar Solutions (If Requested)

阶段4：研究同类解决方案（若用户要求）

Only run when user explicitly chose research in Phase 3.

仅当用户在阶段3明确选择研究时执行此步骤。

4a. Perplexity Query

4a. Perplexity查询

mcp__perplexity-ask__perplexity_ask({
  messages: [{
    role: "user",
    content: "How do leading [industry] products implement [feature type]? Include architectural patterns, UX approaches, and trade-offs. Focus on [tech stack] implementations."
  }]
})

mcp__perplexity-ask__perplexity_ask({
  messages: [{
    role: "user",
    content: "How do leading [industry] products implement [feature type]? Include architectural patterns, UX approaches, and trade-offs. Focus on [tech stack] implementations."
  }]
})

4b. Follow Citations

4b. 跟进引用来源

After Perplexity response, WebFetch top 2-3 relevant sources:

WebFetch(url="<citation-url>", prompt="Extract implementation details, code patterns, and lessons learned for [feature]")

在获取Perplexity的回复后，使用WebFetch工具获取排名前2-3的相关来源内容：

WebFetch(url="<citation-url>", prompt="Extract implementation details, code patterns, and lessons learned for [feature]")

4c. Synthesize Findings

4c. 整合研究结果

Present research summary before asking approach preference:

markdown

undefined

在询问用户方案偏好前，先呈现研究总结：

markdown

undefined

Research Findings

研究结果

Common patterns:

[Pattern 1]: Used by X, Y. Trade-off: ...
[Pattern 2]: Used by Z. Trade-off: ...

Recommended for our context: [Pattern] because [reasons]

---

通用模式：

针对我们场景的推荐： [模式]，原因是[具体理由]

---

Phase 5: Present Approaches

阶段5：呈现实现方案

Use AskUserQuestion with 2-4 options:

Header	Question	Options
Approach	Which approach fits best?	1. [Recommended] - Description + key trade-off 2. [Alternative] - Description + key trade-off 3. Minimal - YAGNI version

使用AskUserQuestion工具提供2-4个选项：

标题	问题	选项
实现方案	哪种方案最符合需求？	1. [推荐方案] - 描述 + 核心权衡点 2. [替代方案] - 描述 + 核心权衡点 3. 极简版 - 遵循YAGNI原则的简化版本

Approach Template

方案模板

For each option, briefly cover:

What: Core implementation
Trade-offs: Complexity vs flexibility, Now vs later
Fits when: Scenario where this shines

每个选项需简要涵盖：

内容：核心实现方式
权衡点：复杂度与灵活性的平衡、短期与长期的取舍
适用场景：该方案的优势场景

Phase 6: Validate Design Incrementally

阶段6：逐步验证设计

Present design in sections (~200-300 words each). After each section, use AskUserQuestion:

Header	Question	Options
Validate	Does this [section] look right?	1. Yes, continue - Move to next section 2. Needs changes - I'll explain 3. Go back - Revisit earlier decisions

按分段（约200-300字）呈现设计内容。每段结束后，使用AskUserQuestion工具：

标题	问题	选项
验证	这个[分段]的设计是否合理？	1. 是，继续 - 进入下一个分段 2. 需要修改 - 我会说明具体调整点 3. 返回上一步 - 重新审视之前的决策

Design Sections

设计分段

Architecture Overview - Components, responsibilities, relationships
Data Flow - How information moves through the system
API/Interface - External contracts and user interactions
Error Handling - Failure modes and recovery strategies
Testing Strategy - How to verify it works

架构概述 - 组件、职责、相互关系
数据流 - 信息在系统中的流转路径
API/接口 - 外部契约与用户交互方式
错误处理 - 故障模式与恢复策略
测试策略 - 验证功能有效性的方法

YAGNI Checkpoints

YAGNI检查点

At each section, actively challenge:

"Do we need this now, or is it speculative?"
"What's the simplest version that solves the problem?"
"Can we defer this complexity?"

在每个分段，主动提出质疑：

“我们现在就需要这个功能吗，还是只是推测性需求？”
“解决该问题的最简版本是什么？”
“我们能否推迟这种复杂度？”

Phase 7: Document and Next Steps

阶段7：文档记录与后续步骤

7a. Write Design Document

7a. 撰写设计文档

Write(
  file_path="docs/plans/YYYY-MM-DD-<topic>-design.md",
  content="# [Feature] Design\n\n## Problem\n...\n## Solution\n...\n## Architecture\n..."
)

Write(
  file_path="docs/plans/YYYY-MM-DD-<topic>-design.md",
  content="# [Feature] Design\n\n## Problem\n...\n## Solution\n...\n## Architecture\n..."
)

7b. Commit Design

7b. 提交设计文档

bash

git add docs/plans/*.md && git commit -m "docs: add [feature] design document"

bash

git add docs/plans/*.md && git commit -m "docs: add [feature] design document"

7c. Implementation Handoff

7c. 实现交接

Use AskUserQuestion:

Header	Question	Options
Next steps	Ready to proceed with implementation?	1. Create worktree - Isolated workspace via using-git-worktrees 2. Create plan - Detailed implementation steps 3. Done for now - Just save the design

使用AskUserQuestion工具：

标题	问题	选项
下一步	准备好进入实现阶段了吗？	1. 创建工作树 - 通过using-git-worktrees创建独立工作区 2. 制定计划 - 详细的实现步骤 3. 暂告一段落 - 仅保存当前设计文档

Methodology Reference

方法论参考

This skill incorporates proven brainstorming techniques:

Technique	How It's Used
Starbursting (5WH)	Structured questions in Phase 2
Design Thinking	Empathize (context) → Define (WHY) → Ideate → Prototype (design sections)
SCAMPER	For modifications: Substitute, Combine, Adapt, Modify, Put to other use, Eliminate, Reverse
Reverse Brainstorming	"How could this fail?" during validation
Mind Mapping	Architecture section visualizes relationships

本技能整合了经过验证的头脑风暴技术：

技术方法	应用方式
星爆式提问法（5WH）	在阶段2中用于结构化提问
设计思维	共情（上下文）→ 定义（问题）→ 构思→ 原型（设计分段）
SCAMPER法	针对修改类需求：替代、组合、适配、修改、复用、删除、反转
反向头脑风暴	在验证阶段提出“如何让这个功能失败？”的问题
思维导图	在架构分段中可视化组件间的关系

Examples

示例

/brainstorming-ideas                    # Start open-ended brainstorm
/brainstorming-ideas user notifications # Brainstorm notification feature
/brainstorming-ideas auth flow          # Brainstorm authentication changes

Execute this collaborative brainstorming workflow now.

/brainstorming-ideas                    # 启动开放式头脑风暴
/brainstorming-ideas user notifications # 针对用户通知功能进行头脑风暴
/brainstorming-ideas auth flow          # 针对认证流程变更进行头脑风暴

立即执行此协作式头脑风暴工作流。