spec-drift-detection

Spec-implementation drift occurs when code changes deviate from the approved specification. You detect this by comparing touched files, public contracts, and security considerations against the spec manifest to identify gaps and enforce scope.

To validate changes against a spec manifest, trigger a drift check during the post-implementation or pre-review phase. This compares the actual diff against declared scope, change manifests, and success criteria to generate an auditable compliance report.

Yes, drift detection requires an existing spec manifest located under the docs/specs directory. Without this approved spec manifest present in the repository, the tool cannot compare touched files or verify scope compliance.

You can automate compliance reporting by running drift detection on your current branch. It validates public contracts and security implications against the diff, producing auditable drift reports suitable for gate decisions.

The best way to prevent scope creep is enforcing drift detection during pre-review phases. Comparing the actual diff against the approved spec manifest ensures code changes align exactly with declared scope and success criteria.