openspec-verify-change

To verify implementation against change artifacts, you can generate a prioritized verification report that checks task completion, requirement coverage, and design adherence to surface any inconsistencies before archiving. The report highlights critical gaps, warnings, and suggestions.

Spec-driven change validation compares delta specs and task checkboxes against the codebase to find missing or partially implemented requirements. It checks scenario coverage and design adherence to surface divergence between the planned intent and the actual implementation before archiving.

Requirement coverage and task completion checks compare your delta specs and task checkboxes against the codebase to identify unfinished work and missing requirements. This process yields a prioritized report highlighting critical gaps, warnings, and suggestions for incomplete implementations.

Yes, reviewing scenario coverage and design adherence requires openspec CLI access. The CLI is used to list changes, inspect status, load context files, and generate the prioritized verification report that surfaces divergences between your design intent and implementation.

The best way to surface completion gaps before archiving is to run a structured change validation review. This checks task checkboxes, compares delta specs against the codebase, and validates scenario coverage to generate a prioritized report of critical gaps and warnings.

Implementation diverges from planned design artifacts when scenario coverage and design adherence checks surface inconsistencies between the delta specs and the codebase. A structured change validation report identifies these specific critical gaps, warnings, and missing requirements.