openspec-verify-change

Code change verification checks implementation against delta specs, tasks, and design before archiving. It maps requirements to code and tests, assessing completeness and coherence to generate a structured report with prioritized findings.

Completeness checks for task completion and delta-spec coverage validate whether implementation tasks and design decisions are fully addressed. The process maps requirements to code and tests, generating a structured verification report.

Change verification handles missing artifacts through graceful degradation, continuing the assessment even when one or more design documents or artifacts are unavailable, while still reporting on available coverage.

Code review findings are prioritized into CRITICAL, WARNING, and SUGGESTION levels to enforce actionable remediation. The structured verification report highlights severity so developers can address the most important issues first.

Run change artifact verification before archiving changes containing delta specs and artifacts. This reduces the risk of incomplete or inconsistent changes entering the repository by validating scenario coverage and test presence.

A change verification report includes completeness checks, correctness verification, scenario coverage assessment, and coherence validation. It provides prioritized CRITICAL, WARNING, and SUGGESTION findings to guide actionable remediation.