spec-driven-development
Guides writing and approving a structured specification with objectives, boundaries, and success criteria before any code is implemented.
What it does
Creates specs before coding. Use when starting a new project, feature, or significant change and no specification exists yet. Use when drafting a PRD or requirements document with objectives and scope, or when requirements are unclear, ambiguous, or only exist as a vague idea. Use when a single requirement spans several independently testable capabilities and needs decomposing into a capability map of modules before specifying.
Quality judgment
Exceptionally thorough: gated four-phase workflow with explicit stop conditions, capability-map decomposition, spec template, boundaries, rationalization counterarguments, and verification checklist. Triggers are concrete with clear negative triggers; minor reliance on external skills slightly limits standalone use.