openspec-verify-change

Verifying code changes against specifications involves mapping requirements to source code, tests, and design decisions. This validation flow generates a structured report covering completeness, correctness, and coherence before archiving.

Change artifact verification validates that code changes implement intended specs and tasks. It checks alignment between design deltas and actual implementation to ensure coherence before archiving.

Yes, validating change implementation requires the openspec CLI. It needs access to delta specs, context artifacts, and source code to load artifacts, apply change context, and map requirements to code.

To check if a code change is complete and coherent before archiving, run a verification flow that validates alignment between change artifacts and implementation. It produces a structured report covering completeness, correctness, and coherence.

A structured verification report for code changes includes assessments of completeness, correctness, and coherence. It maps requirements to code, tests, and design decisions, providing actionable recommendations.

You can validate design delta and task implementation without full manual code review by using automated verification. It maps change artifacts to source code and tests to generate a structured coherence report.