openspec-verify-change

Verifying code changes before archiving involves analyzing task checklists, delta spec requirements, and design decisions to assess completeness, correctness, and coherence, producing a structured report with critical, warning, and suggestion findings.

Change artifact verification is the process of validating that an implementation matches defined specs, tasks, and design documents to ensure accuracy, coherence, and completeness before archiving a change.

Checking task checklist completion against delta specs involves cross-referencing checked task artifacts against explicit requirements and scenario coverage within delta specs to validate correctness and completeness.

Yes, you can generate a verification report for incomplete change implementations that highlights gaps in completeness, correctness, and coherence, outputting critical, warning, and suggestion findings to address before archiving.

No, design documents are optional for running a change verification check; the process applies to changes with delta specs and task artifacts, using design documents if available to assess coherence.