openspec-verify-change

To verify change implementation completeness before archiving, analyze change artifacts like specs and tasks to ensure the code matches documented requirements, parsing delta specs and checking task completion checkboxes for accurate coverage.

Openspec-driven change verification evaluates implementation correctness and coherence by mapping delta spec requirements to code evidence, comparing design.md decisions against actual code, and producing a structured report with CRITICAL, WARNING, and SUGGESTION issues.

Check spec coverage and design coherence by parsing delta specs under openspec/changes/<change>/specs/, mapping requirements to code evidence, and evaluating design.md decisions against the implementation to flag any architectural deviations.

When multiple changes exist, you can interactively select a specific change name to verify, allowing the system to load the corresponding artifacts, perform completeness checks, and return a detailed verification report for that selected change.

The best way to identify incomplete tasks is to validate task completion against tasks.md, specifically checking for unchecked checkboxes marked with [ ] versus completed ones marked with [x] to ensure all required work is finished.

Implementation deviations from the design document are flagged by comparing design.md decisions against the actual implementation, generating WARNING or CRITICAL issues in the structured verification report with concrete recommendations to resolve the discrepancies.