openspec-verify-change

Implementation verification involves comparing source code evidence against change specs, tasks, and design notes to confirm completeness, correctness, and coherence. This process catches missing work, incorrect behavior, and process drift before archiving a feature branch.

Requirement coverage analysis compares change requirements against actual code evidence to identify gaps. It checks whether every specified requirement has corresponding implementation proof, ensuring no intended functionality is missing from the final source code.

Task completion auditing confirms checklist items are finished and flags anything still open. A release manager uses this to review a completed feature branch against its tasks, ensuring all required work is truly done before archiving.

Design consistency validation reviews implementation against design decisions and project patterns to detect inconsistencies. This ensures the codebase adheres to established architectural choices and maintains coherence with the intended project design.

Spec-driven change review requires access to change specs, tasks, design notes, and source code evidence. These artifacts provide the baseline needed to confirm implementation completeness, correctness, and coherence before the change is archived.