openspec-verify-change

To verify code changes against design specs, parse delta specs and tasks to identify gaps in requirement coverage, scenario validation, and design adherence. This generates a structured report highlighting critical gaps with concrete remediation steps and file path references.

Change verification in an openspec workflow is the process of validating that an implementation matches change artifacts, ensuring completeness and coherence. It assesses task completion by parsing tasks.md and checkbox states against the loaded delta specs.

You can check task completion by parsing tasks.md files and evaluating checkbox states against the openspec context. This validates whether implemented changes fully cover the defined tasks and requirements before archiving.

Yes, you can detect design adherence and code pattern inconsistencies by evaluating delta specs against the implementation. The verification process flags pattern inconsistencies and provides targeted remediation with specific file paths and line references.

No, openspec-verify-change does not require external dependencies to run. It operates directly on delta changes loaded via the openspec workflow, requiring only the change name to generate the verification report.

The best way to report gaps between implemented code and specifications is to produce a structured verification report. This report highlights critical gaps, suggests concrete remediation with file paths and line references, and flags any design or pattern inconsistencies.