What problem does it solve? Turning a fuzzy, exploratory idea into a concrete, testable specification is hard without structure. This Skill enforces a disciplined seven-phase brainstorm protocol that draws requirements out through dialogue, evaluates candidate approaches, and produces a reviewed spec before any planning begins. ## Core Features & Use Cases - Seven-Phase Protocol: Runs context scan, optional council advisory, one-question-at-a-time dialogue, approach comparison, design drafting, spec writing with reviewer sign-off, QA gate selection, and transition handling in strict order. - Clarification Funnel: Classifies uncertainties (self_resolved, critic_resolved, research_needed, user_decision, deferred) with an overconfidence guard and research timeout so only true blockers surface as [NEEDS CLARIFICATION] markers. - Mandatory QA Gate Dialogue: Presents eleven QA gates, parallel coder count, commit frequency, and auto-proceed as one unified user decision, recording elections in .swarm/context.md before planning. - Use Case: A user says "help me think through adding real-time collaboration to our app." The Skill maps the codebase, asks focused questions with defaults, presents 2-4 architectural approaches, drafts a WHAT/WHY spec reviewed by an independent reviewer, and captures QA gate choices before handing off to planning. ## Quick Start Ask the agent to brainstorm your feature idea, for example by saying "let's brainstorm adding audit logging to the admin panel," and answer the focused questions it asks one at a time.
