openspec-verify-change

To verify code changes match design specifications, you check implementation artifacts against change specs, task lists, and design notes. This surfaces incomplete tasks and missing requirements as critical issues before archiving or releasing.

Spec compliance verification is the process of confirming an implementation fully matches change artifacts and requirements. It reduces regressions by parsing task checkboxes and mapping requirements to actual codebase implementations.

Yes, you can generate a verification report with partial artifacts like tasks only or tasks and specs. The process gracefully degrades by operating with available files and documenting any checks that were skipped due to missing context.

Yes, you need the openspec CLI to check task completion and requirement coverage. It is required to list changes, fetch change context, and export the artifacts needed to perform the verification analysis.

Correctness mapping identifies divergences by searching the codebase for requirement implementations and comparing them against delta specs. It highlights missing scenario coverage and flags any mismatches as actionable warnings.

The best way to enforce code review and design adherence is to run a coherence analysis comparing design decisions against code patterns. This issues suggestions for style deviations and outputs a structured report for gating releases.