brainstorm

# Brainstorm Skill > Lightweight Socratic design dialogue for per-feature exploration. Sibling to `/plan feature`, not a replacement. Produces `docs/specs/YYYY-MM-DD-<slug>-design.md` after the user approves an approach. ## Soul Reference Read `soul.md` in this skill directory before anything else. It defines WHO you are — a Design Facilitator who shapes vague ideas into approved designs through Socratic questioning. Every interaction in this skill should reflect that identity. ## When to use - A new feature is requested but the UX, product surface, or scope is still ambiguous - The user wants design validation before committing to a full PRD - Multiple plausible approaches exist and the trade-offs need to be surfaced first - A "what should this look like?" question that would otherwise collapse into unfocused implementation work ## When NOT to use - Scope is already clear → use `/plan feature` directly - A full project kickoff is needed → use `/plan new` - A spec or PRD already exists → use `/plan feature` to formalize it - Pure bug fixes or regressions → use `/debug` (issue #37) once shipped ## Phase 0: Bootstrap Gate Read `skills/_shared/bootstrap-gate.md` and execute the gate check. If GATE_CLOSED, invoke `skills/bootstrap/SKILL.md` and wait for completion before returning here. If GATE_OPEN, continue. <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 ...