n8n:spec-driven-development

To keep implementation aligned with specifications, you need a continuous verification process that monitors code changes against spec files. This ensures implementation matches requirements in your specified directory, reducing discrepancies and improving code quality.

Spec-driven development is a process where specifications dictate implementation scope and requirements. It guides development by providing a reference point for consistent coding practices, ensuring features are built according to predefined specs in a specified directory.

You update specifications by modifying spec files as implementation progresses. This ensures that any changes in scope or requirements are reflected in the specification directory, maintaining alignment between the actual code and the documented specs.

Yes, specification management requires a specified directory, such as `.agents/specs/`, where your spec files are located. You need access to this codebase structure and the ability to execute commands within the directory to verify alignment.

The best way to verify code and spec alignment is to run a spec verification pass after completing your work. This continuous verification checks for discrepancies between the implementation and the specifications in your directory.

Discrepancies occur when implementation drifts from specs without updates. Regularly checking for alignment and updating specifications as implementation progresses prevents these mismatches and ensures consistent development practices.