brainstorminglisted

> **Ported here, and some of what it names is not.** This skill comes from upstream, where it > sits beside sibling skills this port does not vendor. Any `superpowers:<name>` or > `elements-of-style:<name>` reference below that does not match a skill you actually have is > **not available here** — do not try to invoke it. Where one is named as a required step, do > the work it describes directly instead, or use the closest skill that is installed. Run > `ls ~/.claude/skills` to see what you have. # Brainstorming Ideas Into Designs 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> ## Anti-Pattern: "This Is Too Simple To Need A Design" 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. ## Checklist You MUST create a task for each of th