openspec-verify-change

To validate code changes against delta specs before archiving, you can run an openspec verification flow to compare code implementations with task artifacts, measure completeness, and generate a structured verification report for audit readiness.

Spec-validation for code review is the process of verifying that code changes match defined change artifacts. It works by searching the codebase for implementation evidence, comparing it against delta specs and design documents, and generating a structured verification report with actionable guidance.

You generate a verification report by listing changes with openspec list --json, selecting a target change, and applying it with openspec instructions apply --change <name>. This produces a structured report measuring completeness, correctness, and coherence of the implementation.

Yes, change-verification supports repeatable validation workflows for QA and compliance reviews. It provides audit readiness by generating structured verification reports that identify missing or divergent elements between code implementations and change artifacts.

When implementation evidence is missing from the codebase, the verification process identifies these divergent elements and provides actionable guidance on the gaps. The generated structured verification report details exactly what is missing to help resolve discrepancies before archiving.