todou-brainstormlisted

# Brainstorming Ideas Into Designs (todou edition) Help turn ideas into fully formed designs and specs through natural collaborative dialogue. The one essential difference from plain /brainstorm: **the dialogue lives on a todou issue** — every question, answer, and proposal revision stays in the timeline, so anyone later (including the agent implementing it, likely you) can replay the decisions. Start by understanding the current project context, then ask questions to refine the idea. Once you understand what you're building, **write the design as a spec and let the review gate be the approval step** — the design does not get narrated into a comment first. **All questions to the user follow the "Asking the user questions" section of `/todou-cli`** (numbered-option comments + `issue watch` for replies) — not repeated here. <HARD-GATE> Do NOT invoke any implementation skill, write any code, scaffold any project, or take any implementation action until the user has approved the spec at the review gate. 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 push it as a spec and get it approved. ## Checklist You MUST create a