brainstorming

To turn a vague idea into an approved design spec, you need a pre-implementation brainstorming workflow that clarifies requirements, proposes design options, and gates execution until a written design document is approved by stakeholders.

The best way to prevent wasted implementation is to enforce early alignment on intent and constraints using a brainstorming workflow that blocks code generation until a concrete design spec is reviewed and explicitly approved.

You refine product requirements by using a workflow that asks a single clarifying question at a time to progressively discover constraints, then proposes 2-3 design approaches with trade-offs before any implementation begins.

No, a strict safety gate blocks any code generation, scaffolding, or implementation actions while brainstorming. You must review and approve the committed design document before execution control is released.

After finishing requirements discovery, the design document is automatically written and committed to the default location at `docs/superpowers/specs/YYYY-MM-DD-<topic>-design.md` for user review and future reference.

After you approve the design spec, the brainstorming workflow transitions control by invoking the `writing-plans` skill to produce a detailed implementation plan for the approved design.