openspec-verify-change

To verify code changes against specs before archiving, you cross-check delta specs, tasks, and design artifacts against the codebase. This ensures implementation completeness and coherence, producing a structured report with actionable remediation steps.

Change artifact verification is the process of validating that an implementation aligns with its specs, tasks, and design documents. It evaluates completeness, correctness, and coherence to guarantee reproducibility and auditability before archiving.

Yes, you can audit OpenSpec delta specs against your codebase by running a verification workflow. It evaluates the workflow context, identifies alignment gaps, and generates a structured report documenting findings and risk levels.

You generate a structured verification report by providing the change name to the verification workflow. It scores completeness, correctness, and coherence, then outputs priorities, summaries, and suggested remediations to guide archiving decisions.

The best way to ensure implementation completeness before archiving specs is to perform three-dimensional verification. This cross-checks actual codebase changes against defined artifacts, guaranteeing auditability and documenting any identified risks.