brainstorming

To turn a vague product idea into an approval-ready design spec, you can use a context-first brainstorming workflow that asks clarifying questions, presents 2-3 design approaches with trade-offs, and writes a committed spec for user approval.

The best way to clarify requirements before component implementation is through a question-by-question collaboration flow that hard-gates coding actions, ensuring scope and constraints are fully defined before transitioning to writing implementation plans.

Approval gating during architecture planning works by blocking implementation actions until the user explicitly reviews and approves a proposed design, preventing wasted engineering effort on unscoped or ambiguous feature creation.

Yes, you can generate visual mockups using an optional browser-based companion tool that creates diagrams and visual aids to improve understanding alongside the written spec documentation.

Committed design specs are stored as written documents under the docs/superpowers/specs/ directory in your repository, allowing for structured review loops and future reference.

Yes, the brainstorming flow explores existing project context by analyzing current files, docs, and recent commits before proposing any design options, ensuring recommendations are grounded in your actual codebase.