openspec-verify-change

To verify implementation matches specs before archiving, compare task checklists and spec requirements against codebase evidence to identify unfinished work, uncovered scenarios, and design drift. This completeness, correctness, and coherence assessment confirms archive readiness and reduces missed requirements.

Spec-driven change verification for release management is the process of tracing each requirement and scenario to implementation evidence. It produces a completeness, correctness, and coherence assessment that helps release managers identify missing tasks or design drift before approving a change.

Check for incomplete tasks and scenario coverage gaps by reading task lists, specs, and design notes, then tracing them to code evidence. The review reports mismatches between intended change artifacts and the actual implementation to highlight uncovered scenarios.

Yes, you can use this spec review approach for design validation and coherence checking. It evaluates whether the implementation follows the stated design and remains consistent with project patterns, providing a coherence assessment that flags design drift before archiving.

To perform an archive-readiness check, you need to provide the change artifacts including tasks, specs, design notes, and code evidence. The verification process reads these inputs to compare requirements against the implementation and report any mismatches.

Implementation reports mismatches against change specs when the code evidence does not fully satisfy the task checklists, scenario coverage, or design adherence requirements. The verification highlights exactly where the implementation drifts from the stated artifacts before archiving.