brainstorm
Compare original and translation side by side
🇺🇸
Original
English🇨🇳
Translation
ChineseBrainstorm
头脑风暴
Transform vague ideas into precise, actionable outputs through adaptive structured questioning. The skill adjusts its depth and output format based on what the user actually needs — from quick idea generation to thorough prompt engineering.
通过自适应结构化提问将模糊的想法转化为精准、可落地的输出。本技能会根据用户的实际需求调整提问深度和输出格式,覆盖从快速生成创意到完整prompt工程的全场景。
Quick Start
快速开始
- User provides a request (vague idea, brainstorm request, or prompt to improve)
- Triage — Classify into one of three modes: Prompt, Explore, or Focused
- Run the appropriate discovery flow (3–7 questions depending on mode)
- Produce the right output type for the mode
- Offer next steps
- 用户提交请求(模糊的想法、头脑风暴请求或需要优化的prompt)
- 分流 — 归类为三种模式之一:Prompt、Explore或Focused
- 运行对应的探索流程(根据模式不同提问3–7个问题)
- 产出适配对应模式的输出内容
- 提供后续步骤选项
Tools
工具
| Tool | Purpose |
|---|---|
| Ask the user ONE question at a time. Use |
| Find references when the user has none and references would genuinely help. |
| Delegate to Plan subagent when the user wants an implementation plan. Use |
| 工具 | 用途 |
|---|---|
| 每次向用户提出ONE问题。尽可能使用 |
| 当用户没有参考资料且参考资料确实能提供帮助时,搜索相关参考内容。 |
| 当用户需要落地计划时,委派给计划子Agent,需传入参数 |
Core Principles
核心原则
- Don't answer before you understand. The urge to help immediately produces generic output. But "understand" doesn't mean "ask 13 questions" — it means knowing enough to be specific.
- One question at a time via . Multiple questions get shallow answers. Never embed questions in plain text — always use the tool.
AskUserQuestion - Prefer multiple choice. Provide an array when the answer space is predictable. Choices are faster to answer, reduce cognitive load, and reveal preferences. Use open-ended only when the answer truly can't be predicted.
options - Mirror the user's language. Don't introduce jargon they didn't use.
- Ask about life, not the domain. Constraints, risks, and deal-breakers require zero domain knowledge but eliminate wrong paths decisively.
- Never re-ask what's already known. Track information from the initial prompt and all answers.
- Respect the user's time. Match question depth to request complexity. A casual "help me brainstorm" doesn't need the same rigor as "craft a detailed prompt."
- 理解需求前不要作答:急于立刻提供帮助会产出通用化的结果,但“理解”不等于“问13个问题”,而是掌握足够信息来产出针对性内容即可。
- 通过每次只提1个问题:同时提多个问题只会得到浅层回答。永远不要在普通文本中嵌入问题,必须使用该工具提出。
AskUserQuestion - 优先使用多选形式:当答案范围可预测时,提供数组作为选项。选择类问题回答速度更快,可降低认知负担,同时能明确用户偏好。仅当答案完全无法预测时才使用开放式问题。
options - 复用用户的表述方式:不要引入用户没提到过的术语。
- 询问实际场景而非领域知识:约束条件、风险、不可接受的底线不需要任何领域知识就能了解,但能直接排除错误路径。
- 永远不要重复询问已知信息:记录初始prompt和所有用户回答中的信息。
- 尊重用户的时间:提问深度要和请求复杂度匹配。随意的“帮我头脑风暴下”不需要和“编写详细prompt”一样严谨。
Triage — Choosing the Right Mode
分流 — 选择合适的模式
Before asking any questions, read the user's request and classify it into one of three modes. This happens internally — don't ask the user which mode they want.
提出任何问题前,请先阅读用户的请求并归类为三种模式之一。该步骤在内部完成,不要询问用户想要哪种模式。
Prompt Mode
Prompt Mode
When: User explicitly wants to create or improve a prompt, or needs a comprehensive brief for another AI/tool/person.
Signals: "improve this prompt", "help me write a prompt", "ช่วยคิด prompt", "I want to ask Claude to...", mentions using the output with another AI.
Flow: Full discovery (5–7 questions across Goal → Direction → Context → Criteria)
Output: Improved Prompt + Discovery Summary
适用场景: 用户明确想要创建或优化prompt,或需要为其他AI/工具/人员提供完整的需求说明。
触发信号: "improve this prompt"、"help me write a prompt"、"ช่วยคิด prompt"、"I want to ask Claude to..."、提到要将输出和其他AI搭配使用。
流程: 完整探索(5-7个问题,覆盖目标→方向→上下文→评估标准)
输出: 优化后的Prompt + 探索总结
Explore Mode
Explore Mode
When: User wants to brainstorm ideas, explore possibilities, or think through something open-ended.
Signals: "brainstorm", "help me think", "ช่วยคิดหน่อย", "I want to build something but...", "what should I...", "any ideas for..."
Flow: Light discovery (3–5 questions) — understand goals + constraints quickly, then generate ideas
Output: Curated ideas/options with trade-offs, then offer to go deeper on the chosen one
适用场景: 用户想要头脑风暴创意、探索可能性、或梳理开放式问题的思路。
触发信号: "brainstorm"、"help me think"、"ช่วยคิดหน่อย"、"I want to build something but..."、"what should I..."、"any ideas for..."
流程: 轻量探索(3-5个问题)——快速了解目标+约束,然后生成创意
输出: 带优劣势的精选创意/选项,随后提供针对选中方向深度探索的选项
Focused Mode
Focused Mode
When: User has a specific problem with existing context and wants strategies or recommendations.
Signals: Prompt already contains specifics (numbers, tech stack, current situation). User says "brainstorm วิธี...", "how to reduce...", "what's the best approach to..."
Flow: Targeted discovery (2–4 questions) — only ask about genuine unknowns, skip what's already stated
Output: Actionable strategies/recommendations with priorities and estimated impact
适用场景: 用户有明确的特定问题,已有相关上下文,需要解决策略或建议。
触发信号: 请求中已经包含具体信息(数字、技术栈、当前现状);用户说"brainstorm วิธี..."、"how to reduce..."、"what's the best approach to..."
流程: 定向探索(2-4个问题)——仅询问确实未知的信息,跳过已经明确的内容
输出: 带优先级和预估影响的可落地策略/建议
Workflow by Mode
各模式工作流
For detailed questioning patterns, techniques, and examples per phase, see references/QUESTIONING-GUIDE.md
如需了解各阶段的详细提问模式、技巧和示例,请查看references/QUESTIONING-GUIDE.md
Prompt Mode — Full Discovery
Prompt Mode — 完整探索
The most thorough path. Use all phases when the user needs a well-crafted prompt.
Phase 1 — Receive: Acknowledge the request. Say something like: "I'll help you craft that prompt. Let me ask a few questions to make it specific to your situation."
Phase 2 — Goal: What does the user want the prompt to achieve? Get to a one-sentence goal with at least one measurable indicator. (1–2 questions)
Phase 3 — Direction: What must NOT happen? What approaches exist? Propose 2–3 viable approaches with trade-offs after gathering constraints. Lead with your recommendation. (1–2 questions + proposal)
Phase 4 — Reference (optional): Only if references would genuinely help (e.g., style/design requests). Ask if they have examples. If none and it would help, use . Skip entirely for straightforward requests. (0–1 questions)
WebSearchPhase 5 — Context: Surface practical constraints: time, budget, skills, team, environment. Flag contradictions with the goal gently. (1–2 questions)
Phase 6 — Criteria: Define what "good" means. Force-rank if more than 3 criteria. (1 question)
Phase 7 — Synthesize: Draft the improved prompt with this structure:
undefined最全面的路径。当用户需要精心打磨的prompt时使用所有阶段。
阶段1 — 接收请求: 确认收到请求,示例表述:"我会帮你编写对应的prompt,我先问几个问题,让内容更适配你的实际情况。"
阶段2 — 目标: 用户希望这个prompt达成什么效果?需要得到至少包含1个可衡量指标的单句目标描述。(1-2个问题)
阶段3 — 方向: 哪些情况是绝对不能出现的?有哪些可行的实现路径?收集约束后提出2-3个带优劣势的可行方案,优先给出你的推荐。(1-2个问题 + 方案提议)
阶段4 — 参考资料(可选): 仅当参考资料确实能提供帮助时(比如风格/设计类请求)才启用。询问用户是否有示例,如果没有且参考有价值则使用。简单请求直接跳过本阶段。(0-1个问题)
WebSearch阶段5 — 上下文: 梳理实际约束:时间、预算、技能、团队、使用环境。温和地指出和目标冲突的内容。(1-2个问题)
阶段6 — 评估标准: 定义“好”的标准,如果超过3个标准请让用户排序。(1个问题)
阶段7 — 整合输出: 按照以下结构编写优化后的prompt:
undefinedImproved Prompt
Improved Prompt
[The refined, specific prompt incorporating all discovered information]
[融合了所有收集到的信息的精炼、具体的prompt]
Discovery Summary
Discovery Summary
Goal: [One sentence with measurable indicator]
Direction: [Chosen approach and key constraints]
Context: [Practical constraints: time, budget, skills, environment]
Criteria: [Ranked evaluation criteria]
The improved prompt must be self-contained, include all constraints inline, and be specific enough that any AI produces a targeted answer.
Present it and ask: *"Does this capture what you need? Anything to adjust?"* Iterate if needed.
---Goal: [带可衡量指标的单句目标]
Direction: [选中的方案和核心约束]
Context: [实际约束:时间、预算、技能、使用环境]
Criteria: [排序后的评估标准]
优化后的prompt必须是自包含的,所有约束都内嵌在内容中,足够具体到任何AI都能产出针对性的回答。
提交内容后询问:*"这个是否符合你的需求?有需要调整的地方吗?"* 按需迭代。
---Explore Mode — Light Discovery
Explore Mode — 轻量探索
For open-ended brainstorming where the user wants ideas, not a prompt.
Phase 1 — Receive + Quick Goal: Acknowledge, then ask ONE question combining goal + motivation. Example: "What draws you to this — learning, earning, solving a personal problem, or something else?" (1 question)
Phase 2 — Constraints: Ask about deal-breakers and practical limits in 1–2 questions. Combine related constraints (time + budget, or skills + tools) into a single question when natural. (1–2 questions)
Phase 3 — Generate: Based on what you've learned, produce 5–8 concrete ideas organized by theme. Each idea should include:
- What it is (one sentence)
- Why it fits this user's constraints
- One potential challenge
Phase 4 — Narrow: Ask which ideas resonate. Then offer:
- Go deeper on one idea (pivot to Prompt Mode or create a plan)
- Generate more ideas in a specific direction
- Done — take the ideas and go
适用于用户想要创意而非prompt的开放式头脑风暴场景。
阶段1 — 接收请求+快速确认目标: 确认收到请求,然后提出1个同时覆盖目标+动机的问题。示例:"你对这件事感兴趣的原因是什么——学习、盈利、解决个人问题还是其他原因?"(1个问题)
阶段2 — 约束确认: 用1-2个问题询问不可接受的底线和实际限制。自然地将相关约束(时间+预算,或技能+工具)合并为一个问题。(1-2个问题)
阶段3 — 生成创意: 根据收集到的信息,产出5-8个按主题分类的具体创意,每个创意包含:
- 创意内容(单句描述)
- 匹配用户约束的原因
- 1个潜在挑战
阶段4 — 缩小范围: 询问用户对哪些创意感兴趣,然后提供以下选项:
- 深度探索某个创意(切换到Prompt Mode或创建落地计划)
- 针对特定方向生成更多创意
- 结束——用户带走现有创意即可
Focused Mode — Targeted Discovery
Focused Mode — 定向探索
For specific problems where the user already provided good context.
Phase 1 — Acknowledge context: Summarize what you already know from the prompt. Explicitly list what's established so the user sees you're not going to re-ask it.
Phase 2 — Fill gaps: Ask only about genuine unknowns that would change your recommendations. If the prompt is detailed enough, you might ask just 1 question — or even zero and go straight to recommendations. (0–2 questions)
Phase 3 — Strategize: Produce actionable recommendations:
- Prioritized list (quick wins first, then bigger efforts)
- Each item: what to do, estimated impact, effort level, risks
- Clear "start here" recommendation
Phase 4 — Refine: Ask if anything needs adjustment. Offer to create an implementation plan via Plan subagent.
适用于用户已经提供了充分上下文的特定问题场景。
阶段1 — 确认上下文: 总结你从请求中已经了解的信息,明确列出已确认的内容,让用户知道你不会重复提问。
阶段2 — 填补信息缺口: 仅询问会影响你给出推荐的未知信息。如果请求的信息已经足够详细,你可能只需要问1个问题,甚至不需要提问直接给出建议。(0-2个问题)
阶段3 — 输出策略: 产出示可落地的建议:
- 优先级列表(先快速见效的方案,再体量更大的方案)
- 每个条目包含:操作内容、预估影响、投入程度、风险
- 明确的“从这里开始”的推荐
阶段4 — 优化调整: 询问是否有需要调整的内容,提供通过计划子Agent创建落地计划的选项。
Next Step
后续步骤
After delivering the output (regardless of mode), offer next steps using :
AskUserQuestion- Create a Plan — Delegate to Plan subagent with , passing the full output as context
subagent_type: "Plan" - Go deeper — Continue exploring a specific aspect
- Done — End the workflow
交付输出后(无论哪种模式),通过提供后续步骤选项:
AskUserQuestion- 创建计划 — 委派给计划子Agent,传入参数,将完整输出作为上下文传入
subagent_type: "Plan" - 深度探索 — 继续探索特定方向的细节
- 结束 — 终止工作流
Handling Edge Cases
边缘场景处理
User wants to skip questions: Respect it. Produce the best output with what you have. Briefly note what's missing: "Without knowing [X], this might be more generic — but here's what I've got."
User says "I don't know": Offer 2–3 concrete options and let them react. Reactions reveal preferences without requiring expertise.
Contradictions in user's answers: Flag neutrally: "Earlier you mentioned X, but Y seems different. Which should we prioritize?"
Too broad for one session: Suggest splitting. Run the workflow for each piece.
Mode feels wrong mid-conversation: Switch. If you started in Explore Mode but the user clearly wants a detailed prompt, transition to Prompt Mode. No need to restart — carry forward what you've learned.
用户想要跳过提问: 尊重用户选择,用现有信息产出尽可能好的结果,简要说明缺失信息的影响:"由于不了解[X信息],结果可能会更通用,以下是我整理的内容。"
用户说“我不知道”: 提供2-3个具体选项让用户反馈,反馈不需要用户有专业知识就能体现偏好。
用户的回答有矛盾: 中立指出:"之前你提到过X,但现在的Y看起来和它有差异,我们应该优先考虑哪个?"
范围太广无法一次完成: 建议拆分处理,针对每个部分单独运行工作流。
对话中发现模式匹配错误: 直接切换模式。如果你一开始用了Explore Mode但用户明显想要详细的prompt,直接切换到Prompt Mode即可,不需要重启,已经收集的信息可以继续使用。