brainstorminglisted

# Brainstorming Ideas Into Designs Turn ideas into designs through collaborative dialogue, BEFORE any code. Pairs with Brian's `14-independent-idea-engine` and the SUPREME "brainstorm-first" rule. <HARD-GATE> No implementation skill, code, scaffold, or implementation action until a design is presented AND the user approves it. EVERY project, regardless of perceived simplicity. </HARD-GATE> ## "Too simple to need a design" is the trap "Simple" projects (todo list, one-function util, config change) hide the most unexamined assumptions. Design can be a few sentences — but present it and get approval. ## Checklist (one task each, in order) 1. **Explore project context** — files, docs, recent commits. Follow existing patterns. 2. **Offer the visual companion just-in-time** — NOT upfront. Offer (own message) the first time a question is genuinely clearer shown than told; never if no visual question arises. See `visual-companion.md`. 3. **Ask clarifying questions** — one per message, multiple-choice preferred. Purpose / constraints / success criteria. 4. **Propose 2-3 approaches** — trade-offs, lead with your recommendation + why. 5. **Present design** — sections scaled to complexity (sentences → 200-300 words). Approval after each. Cover architecture, components, data flow, error handling, testing. 6. **Write design doc** — `docs/superpowers/specs/YYYY-MM-DD-<topic>-design.md` (user pref overrides path), commit. 7. **Spec self-review** — inline scan: placeholders/TBD, contrad