What problem does it solve? Turning a fuzzy, exploratory idea into a well-formed specification is hard: requirements stay implicit, assumptions go unrecorded, and teams jump to implementation too early. This Skill enforces a disciplined seven-phase brainstorm protocol that draws requirements out through structured dialogue before any spec is committed. ## Core Features & Use Cases - Seven-Phase Protocol: Runs context scan, optional council advisory, one-question-at-a-time dialogue, candidate approach comparison, design drafting, spec writing with reviewer sign-off, and a controlled transition to planning. - Clarification Funnel: Classifies uncertainties (self_resolved, critic_resolved, research_needed, user_decision, deferred_nonblocking), applies an overconfidence guard, and surfaces only surviving items as [NEEDS CLARIFICATION] markers. - Independent Spec Review: Delegates the draft spec to a reviewer agent that flags HOW-encoded requirements, untestable requirements, missing edge cases, and silent assumptions. - Use Case: A user says "let's think through adding multi-tenant support." The Skill maps the codebase, asks up to six focused questions with informed defaults, presents 2-4 candidate approaches with tradeoffs, and produces a reviewed .swarm/spec.md ready for planning. ## Quick Start Ask the architect to brainstorm your idea, for example by saying "brainstorm how we should add audit logging to the API."
