brainstorming

To turn ambiguous ideas into an approved design specification, use a structured discovery-to-approval workflow that clarifies requirements, compares architecture tradeoffs, and gates implementation until user approval is secured.

The best way to clarify requirements for a design spec is through single-question clarification sequencing, exploring project context first to refine purpose, constraints, and success criteria without overwhelming the user.

Comparing architecture tradeoffs involves proposing 2–3 design approaches, recommending one option, and justifying the selection based on specific project constraints and behavioral requirements before finalizing the spec.

Yes, you can use an optional Visual Companion flow during requirements discovery to handle visual questions like mockups and diagrams via a browser-based tool, without forcing visuals when they are not needed.

After getting user approval, you should save the validated design specification by persisting it under the docs/superpowers/specs repository path to ensure it is documented before implementation.

After a design specification is approved and persisted, the workflow transitions to the writing-plans skill for final handoff, ensuring implementation only begins once the validated spec is fully documented.