spec-driven-development

Structured feature development is enforced by requiring the creation and approval of requirements, design, and task documents before coding begins. This iterative process ensures a stable foundation and clear dependencies.

Managing requirements and design documents for iterative development is best handled through YAML document management. This approach structures artifact creation and facilitates collaborative feature development.

Approval gates for requirements and design artifacts are set up using a left-to-right approval process. This ensures each specification document is reviewed and approved before moving to the next development phase.

Feature specifications can be mapped directly to task commands for execution. The workflow maps to commands like `aim spec new` and `decompose_prd` to integrate specification creation with task management.

Spec-driven development works without external dependencies, relying entirely on internal scripts and references to guide the creation of requirements, design, and task artifacts.

Requirements, design, and tasks markdown files are needed when starting a new feature. You initiate the process with `aim spec new` to generate the foundational artifacts for structured execution.