brainstormlisted

# Brainstorm — Design Phase Turn ideas into fully-formed specs through structured dialogue: explore context, assess scope, ask one question at a time, propose approaches, present the design section by section, and hand off to `/flow:plan`. <HARD-GATE> Do NOT invoke `/flow:plan`, write any code, scaffold any files, or take any implementation action until the spec has been written, self-reviewed, and the user has explicitly approved it. </HARD-GATE> --- ## Process Flow ``` Start | v [1. Explore project context] Read CLAUDE.md, project files, recent git log. Note any output path or naming conventions CLAUDE.md specifies. | v [2. Assess scope] Does the request describe multiple independent subsystems? | YES --> Flag decomposition immediately. Do not ask detailed questions yet. | Help the user decompose into sub-projects, then brainstorm the first one. | NO | v [3. Ask clarifying questions] One question per message. Multiple choice preferred. Focus: purpose, constraints, success criteria. | v [4. Auto-detect visual questions] Is this question about layout, mockups, diagrams, or visual comparison? | YES --> Offer visual companion (first time only, its own message). | If accepted: start server, track PID, serve mockup. | Subsequent visual questions in the same session reuse the server. | NO --> Stay in terminal even if companion is active. | v [5. Propose 2-3 approaches] Lead with recommendation. Explain