sdd-workflow

Spec-driven development is a methodology that transforms vague ideas into structured, actionable specifications before code implementation. It uses a 5-step process—Constitution, Specify, Clarify, Plan, and Tasks—to define project principles and feature requirements, ensuring clarity and alignment with project goals.

You define project requirements by creating a specification document through a structured 5-step workflow. This process guides you through establishing a project constitution, specifying feature requirements, clarifying ambiguities, planning technical architecture, and breaking down granular tasks before any code is written.

Yes, the workflow explicitly marks and resolves unclear requirements during the Clarify step of the specification process. By forcing stakeholders to define user stories, acceptance criteria, and technical plans upfront, it prevents guesswork and ensures all stakeholders agree before implementation begins.

The best way to break down features is using the Tasks step within the spec-driven development workflow. After defining the project constitution, feature specifications, and technical plans, the methodology guides you through creating granular, actionable tasks to ensure structured documentation and requirement alignment.

You need to create a project constitution when starting a new complex feature and using spec-driven development. It is the first step of the methodology, allowing you to establish foundational project principles and ensure alignment among stakeholders before moving into feature specification and task breakdown.