spec

Spec-driven development automates your workflow by orchestrating a six-step pipeline that transforms intent into executable specifications, auto-generating tests, guiding implementation, and updating documentation. This process ensures specifications directly drive test creation and validation before deployment.

You can automate test generation by feeding a feature specification into the six-step pipeline, which coordinates the auto-generation of tests based on your provided specs. The workflow pauses at developer-approved gate points to ensure alignment before moving to implementation.

Yes, the spec-driven pipeline applies to feature development, bug fixing, API evolution, and new spec tasks. It coordinates iterative implementation and validation across these scenarios by using gate-controlled deployment to ensure specifications drive the entire process.

Gate-point approvals work by pausing the autonomous execution of the six-step pipeline at predefined checkpoints, requiring developer approval before proceeding to implementation, validation, or deployment. This ensures safety and alignment with the original specifications throughout the workflow.

The best way to keep documentation updated is using a pipeline that integrates documentation updates as a core step. After validation, the workflow automatically updates your docs to reflect the executable specifications, ensuring they remain synchronized with the implemented features.

No external dependencies are required to run this specification orchestration pipeline. It operates autonomously to coordinate the six-step spec-driven workflow, relying only on frontmatter-driven metadata to manage task orchestration and automated testing loops.