spec-driven-development

To write a software specification before coding, draft a structured plan using a six-section template covering Objective, Commands, Project Structure, Code Style, Testing Strategy, and Boundaries to guide development and prevent guesswork.

Spec-driven development is the practice of creating a written specification before coding to align collaborators. Use it when starting new projects, features, or architectural decisions where requirements are unclear or evolving.

Structure a project specification using a four-phase workflow: Specify, Plan, Tasks, and Implement. This enforces structured content across six core sections to align both human and AI collaborators throughout the process.

Yes, you can use specification-driven workflows for evolving requirements because the approach supports living documentation that updates with decisions, ensuring the project plan remains accurate as assumptions change.

The best way to document architectural decisions during software planning is to maintain living documentation within your specification, tracking changes and referencing related SKILLs to reuse established decisions.

A testing strategy section for a new software feature should outline the testing approach within the broader project specification, defining boundaries and expectations to guide both implementation and validation phases.