openspec-verify-change

Verifying implementation against specs involves loading delta artifacts and scanning the codebase for evidence across files, tests, and documentation, producing a structured report with actionable recommendations for archiving decisions.

A change implementation verification report reconciles code, tests, and documentation with delta artifacts to reveal gaps and ensure coherence, providing concrete file references and actionable recommendations to support archiving decisions.

Checking if your codebase matches design specs requires loading available specs and tasks, then scanning the codebase for implementation evidence across files and tests to output a structured report highlighting gaps between artifacts and code.

Yes, you need available specs and tasks to validate a change implementation. The verification workflow applies to changes that have these delta artifacts loaded to ensure the implementation aligns with the design before archiving.

The best way to find gaps between specs and code implementation is to reconcile change artifacts with the codebase, tests, and documentation, producing a concise verification output indicating completeness and coherence for archival decisions.

You should not use an automated spec verification workflow when a change lacks available specs and tasks, as the verification process requires these delta artifacts to load and compare against the codebase for evidence of implementation.