openspec-verify-change

To verify code implementation against OpenSpec change artifacts, you provide the change name and the workflow generates a report checking completeness, correctness, and coherence. This surfaces gaps to prevent misalignment before archiving or merging.

Delta-spec verification checks for task completion coverage, requirement implementation mapping, and scenario coverage. It ensures the implementation matches the OpenSpec design decisions and specs with actionable recommendations.

You check if code matches design decisions before merging by running a coherence verification that validates design adherence and code pattern consistency. This confirms alignment with OpenSpec specs and tasks to surface any gaps.

Yes, you can use automated validation for task completion checks in OpenSpec. The verification workflow evaluates completeness of delta-spec coverage and task completion, applying actionable recommendations to correct any misalignment.

You need to run change verification after implementing a change and before archiving or merging. It confirms alignment with OpenSpec artifacts, preventing spec misalignment and surfacing gaps in requirement mapping or design coherence.

The best way to surface gaps in requirement implementation mapping is through a correctness verification check. This evaluates how well the implementation maps to OpenSpec requirements and scenario coverage, generating a report with actionable recommendations.