brainstorming

A brainstorming workflow for design specs enforces a hard gate against any implementation activity, requiring you to clarify product requirements, evaluate trade-offs, and secure user approval before writing code or scaffolding begins.

You document product requirements by evaluating 2–3 design approaches with explicit trade-offs, selecting one, and committing the validated design spec to a markdown file at docs/superpowers/specs/ to ensure full traceability.

No, you cannot start writing code or scaffolding while finalizing component interface specifications. The workflow enforces a hard approval gate that prevents any implementation activity until the design spec is fully approved.

The best way to align on behavior changes is through a context-first exploration of your current project state, asking clarifying questions one at a time to refine intent and success criteria before transitioning to writing-plans.

No, this design spec workflow requires no external dependencies or tools to function. It operates independently using internal scripts and references to explore your project context and generate the approved design documentation.