openspec-verify-change

To verify a code change against specs before archiving, you run a verification flow that cross-checks the change against delta specs, tasks, and design notes to produce a structured report. This confirms completeness, correctness, and coherence.

Delta-spec verification is the process of cross-checking code changes against change artifacts located under openspec/changes to ensure alignment. You need it before archiving a change to confirm all requirements are addressed and no critical gaps remain.

To generate a change verification report using openspec, you list changes with openspec list --json, select the target change, and apply instructions with openspec instructions apply --change "<name>" --json to review the generated verification output.

Yes, the change verification process checks task completion and design coherence through artifact-aware validation. It considers associated tasks and design notes alongside delta specs to determine completeness and coherence before archiving.

A structured verification report for code changes evaluates dimensions across Completeness, Correctness, and Coherence. It produces a prioritized list of action items and actionable recommendations to address any identified gaps.

Your code change may be failing spec verification before archiving due to gaps in Completeness, Correctness, or Coherence. The verification report identifies missing requirements from delta specs, tasks, or design notes and provides actionable recommendations to resolve them.