openspec-verify-change

To verify code changes match delta specs before archiving, you run a structured verification workflow that cross-checks requirements against the codebase to detect gaps and generate a report. It compares your delta specs, tasks, and design context with the implemented code.

Change artifact verification in the OpenSpec workflow is the process of validating that an implementation matches defined delta specs and design context. It ensures completeness, correctness, and coherence before archiving by cross-checking requirements against the codebase.

You validate task completion by checking tasks.md, status, and delta specs availability to generate a verification report. This process cross-checks requirements in delta specs against the codebase to detect missing scenarios and divergences.

Yes, you can detect missing scenarios and divergences between specs and implemented code by cross-checking requirements in delta specs against the codebase. This identifies gaps and produces a structured verification report with actionable recommendations.

A structured verification report for code changes includes task status, spec coverage, and design coherence details. It provides actionable recommendations to guide remediation where gaps, divergences, or missing scenarios are detected.

You should run change verification on your project before archiving code changes to ensure implementation completeness, correctness, and coherence. It is specifically needed for projects using the OpenSpec workflow to validate delta specs, tasks, and design context against implemented code.