openspec-verify-change

Verify code changes against specs by parsing delta specs, searching implementation code, and generating structured reports that identify mismatches across completeness, correctness, and coherence dimensions.

A completeness check validates that all tasks are addressed and properly covered by delta specs, ensuring no required implementation work is missing before archival.

Check implementation code against design artifacts by running coherence validation, which assesses design adherence and pattern consistency across specs, tasks, and design artifacts to detect structural mismatches.

Yes, openspec verification operates without external dependencies, using internal delta-spec parsing and code search to validate schemas and artifact presence across change artifacts directly.

The best way to identify mismatches is correctness checking, which assesses alignment between requirements defined in delta specs and the actual code implementation to detect deviations before archival.

Run change verification on specs and tasks immediately before archiving a change, ensuring the implementation is complete, correct, and coherent with all defined artifacts to prevent incomplete archival.