brainstorming

To turn a feature idea into an approved design spec before coding, this Skill guides you through a gated, requirement-first workflow with iterative questioning, multiple approaches, and explicit user approval gates before writing a design specification.

Documenting implementation requirements for extending functionality is best handled by clarifying scope, constraints, and success criteria iteratively, then writing a validated design spec to a dated path under docs/superpowers/specs/ for project-context exploration.

To run a spec review loop for architecture documentation, the Skill dispatches a spec reviewer and iterates on the written design spec up to three iterations until the requirements and design are formally approved.

Yes, the design spec workflow supports implementation planning handoff by ensuring you only proceed to invoke writing-plans after the user explicitly approves the written design specification.

You can use this requirement-first workflow for modifying existing systems, changing behavior, and adding new components, as long as scope, constraints, and success criteria are clarified before any coding begins.

A limitation of this gated requirement-first design workflow is that it strictly prevents implementation work until the spec review loop is fully approved, which may delay rapid prototyping for changes with inherently ambiguous or evolving scope.