openspec-verify-change

To verify code implementation against design specifications, you can parse openspec artifacts to check task completion, map requirements to code, validate scenario coverage, and ensure adherence to design decisions before archiving changes.

Spec compliance verification checks for completeness by confirming all tasks are done, correctness by mapping requirements to code and validating scenarios, and coherence by ensuring design adherence and consistency with project coding patterns.

Yes, you need openspec-cli installed and configured, as the verification process operates by parsing openspec artifacts and analyzing your codebase against the associated specifications, tasks, and design documents.

You should run a spec compliance check after developing a new feature based on a specification document and before merging the code, ensuring all aspects of the specification have been implemented correctly and consistently.

The best way to ensure code review covers defined requirement scenarios is to automatically assess correctness by mapping requirements to code and validating that the implementation covers all defined scenarios extracted from openspec artifacts.

Implementation verification fails on design adherence when the codebase diverges from parsed design documents, and fails on pattern consistency when the implementation does not align with established project coding patterns defined in the artifacts.