sdlc-1-spec-driven-development

To prevent architectural drift, enforce a mandatory specification phase before code implementation. This structured approach documents objectives, commands, structure, style, testing, and boundaries to ensure complete alignment between human intent and agent actions.

A gated workflow in the software development lifecycle is a formal review process that blocks irreversible changes. It requires a human engineer to validate the structured specification plan before any actual code implementation can proceed.

To create a structured specification for project initialization, generate documentation covering six mandatory areas: objectives, commands, structure, style, testing, and boundaries. This framework ensures all requirements are clearly defined before development starts.

You need a formal specification phase for feature development when a new feature touches multiple modules or requires architectural changes. It prevents the agent from guessing requirements and making incorrect architectural decisions by enforcing human validation.

Spec-driven development works for existing codebase modifications by applying the gated review process to architectural changes. It forces you to document assumptions and success criteria, preventing bugs and ensuring alignment before writing code.