phxbrainstorm

# Brainstorm — Adaptive Requirements Gathering Interactive interview → research → synthesis loop. Produces structured `interview.md` that `/phx:plan` detects and consumes (skipping clarification). ## Usage ```text /phx:brainstorm Add some kind of notification system /phx:brainstorm Improve authentication security /phx:brainstorm # starts with open question ``` ## Workflow ``` /phx:brainstorm {topic} | v [INTERVIEW] ←──────────────────┐ | | v (sufficient OR user exit) | [DECISION POINT] | ├─ Research ──→ [RESEARCH] ─┘ ├─ Continue interview ──────┘ ├─ Make a plan ──→ STOP (suggest /phx:plan {slug}) ├─ Store & exit ──→ STOP (artifacts saved) └─ Discuss ──→ freeform ──→ [DECISION POINT] ``` ## Phase 1: Adaptive Interview Create `.claude/plans/{slug}/` directory. Start asking ONE question at a time. ### Coverage Dimensions Track coverage across 6 dimensions (0=uncovered, 1=partial, 2=sufficient). **Ask Scope early** — for "optimize X" topics, ask about boundaries (upstream OK? Local-only? CI vs dev?) before research, not during. | Dim | Target | Sufficient signal | |-----|--------|-------------------| | What | Specific behavior/features | Concrete verbs, not "some kind of" | | Why | Problem solved, user need | Clear benefit stated | | Scope | In/out boundaries | Explicit exclusions stated | | Where | Modules, contexts, pages | File paths or context names mentioned | | How | Ap...