openspec-verify-change

To verify code changes against specs, validate that the implementation matches change artifacts by searching delta specs under openspec/changes/<name>/specs and assessing task completion. This generates a structured verification report highlighting completeness, correctness, and coherence.

OpenSpec delta spec verification compares an implementation against specs, tasks, and design context using the OpenSpec CLI. It searches for delta specs, loads available context artifacts, and assesses traceability to determine if a proposed change fully implements the intended artifacts.

Checking spec coverage and task completion involves loading change artifacts and assessing the codebase against them. The verification process outputs a report with actionable recommendations and file references, ensuring coherence before archiving a change.

Yes, you can automate change artifact validation using the OpenSpec CLI by providing a change name to verify. The automated status checks determine completeness and traceability across specs, tasks, and design context, guiding archiving decisions and reducing risk.

Yes, OpenSpec verification works without external dependencies. It independently searches for delta specs, loads context artifacts, and assesses task completion and spec coverage across the codebase to output a structured verification report.

Code changes fail coherence checks when the implementation lacks traceability or does not fully match the intended design specs. The verification report highlights these completeness and correctness gaps, providing actionable recommendations and file references to resolve them.