spec-driven-development

Follow the Specify phase: surface assumptions explicitly, ask clarifying questions, then write a spec covering Objective, Commands, Project Structure, Code Style, Testing Strategy, and Boundaries. Get human approval before moving to planning.

It is a four-phase gated process: Specify, Plan, Tasks, Implement. Each phase requires human review before advancing, and a Phase 0 scope check decomposes multi-capability requests into a capability map first.

Skip it for single-line fixes, typo corrections, or changes where requirements are unambiguous and self-contained. The workflow targets new features, ambiguous requirements, and changes touching multiple files or modules.

Use Phase 0 scope check to create a capability map with stable kebab-case module ids, one-way dependencies, and a build order. Then run the full Specify-to-Implement cycle per module in dependency order.

Yes, the workflow is format-agnostic. If a project already uses OpenSpec or another specification system, keep that tool's artifact format and storage conventions while this skill owns clarification, content, and approval gates.