$ loading_
在创意与实现前梳理用户意图、需求与方案方向，降低返工风险。
复制安装指令，让 AI 自动完成配置 · 推荐新手
请帮我安装 askskill 上的 "brainstorming" 技能： 1. 下载 https://raw.githubusercontent.com/obra/superpowers/main/skills/brainstorming/SKILL.md 2. 保存为 ~/.claude/skills/brainstorming/SKILL.md 3. 装好后重载技能，告诉我可以用了
我要为电商后台新增批量退款功能。请先不要写代码，先通过头脑风暴帮我梳理用户目标、关键场景、边界条件、风险点，以及可行的交互与技术方案。
一份结构化的需求与方案清单，包含目标、场景、限制、风险和实现方向建议。
我要设计一个可复用的日期筛选组件。请先头脑风暴不同使用场景、用户操作习惯、状态设计、可访问性要求，以及组件 API 的设计选项，再给出推荐方案。
多种设计思路的对比分析，以及一个更适合落地的推荐组件方案。
我想修改现有通知系统的发送逻辑。请在改动前先头脑风暴这次变更可能影响的用户体验、业务规则、异常情况、回滚策略和测试重点。
一份变更影响评估与实施前检查清单，帮助安全推进修改。
Help turn ideas into fully formed designs and specs through natural collaborative dialogue.
Start by understanding the current project context, then ask questions one at a time to refine the idea. Once you understand what you're building, present the design and get user approval.
<HARD-GATE> Do NOT invoke any implementation skill, write any code, scaffold any project, or take any implementation action until you have presented a design and the user has approved it. This applies to EVERY project regardless of perceived simplicity. </HARD-GATE>Every project goes through this process. A todo list, a single-function utility, a config change — all of them. "Simple" projects are where unexamined assumptions cause the most wasted work. The design can be short (a few sentences for truly simple projects), but you MUST present it and get approval.
You MUST create a task for each of these items and complete them in order:
docs/superpowers/specs/YYYY-MM-DD-<topic>-design.md and commitdigraph brainstorming {
"Explore project context" [shape=box];
"Visual questions ahead?" [shape=diamond];
"Offer Visual Companion\n(own message, no other content)" [shape=box];
"Ask clarifying questions" [shape=box];
"Propose 2-3 approaches" [shape=box];
"Present design sections" [shape=box];
"User approves design?" [shape=diamond];
"Write design doc" [shape=box];
"Spec self-review\n(fix inline)" [shape=box];
"User reviews spec?" [shape=diamond];
"Invoke writing-plans skill" [shape=doublecircle];
"Explore project context" -> "Visual questions ahead?";
"Visual questions ahead?" -> "Offer Visual Companion\n(own message, no other content)" [label="yes"];
"Visual questions ahead?" -> "Ask clarifying questions" [label="no"];
"Offer Visual Companion\n(own message, no other content)" -> "Ask clarifying questions";
"Ask clarifying questions" -> "Propose 2-3 approaches";
"Propose 2-3 approaches" -> "Present design sections";
"Present design sections" -> "User approves design?";
"User approves design?" -> "Present design sections" [label="no, revise"];
"User approves design?" -> "Write design doc" [label="yes"];
"Write design doc" -> "Spec self-review\n(fix inline)";
"Spec self-review\n(fix inline)" -> "User reviews spec?";
"User reviews spec?" -> "Write design doc" [label="changes requested"];
"User reviews spec?" -> "Invoke writing-plans skill" [label="approved"];
}
The terminal state is invoking writing-plans. Do NOT invoke frontend-design, mcp-builder, or any other implementation skill. The ONLY skill you invoke after brainstorming is writing-plans.
Understanding the idea:
…
在宣称任务完成或修复成功前，先执行验证并用结果佐证结论。
根据需求先拆解多步骤任务，生成清晰可执行的实施计划