Openspec Verify Change

Get the change directory and load artifacts

openspec instructions apply --change "<name>" --json

This returns the change directory and context files. Read all available artifacts from contextFiles.

Initialize verification report structure

Create a report structure with three dimensions:

• Completeness: Track tasks and spec coverage
• Correctness: Track requirement implementation and scenario coverage
• Coherence: Track design adherence and pattern consistency

Each dimension can have CRITICAL, WARNING, or SUGGESTION issues.

Verify Completeness

Task Completion:

• If tasks.md exists in contextFiles, read it
• Parse checkboxes: - [ ] (incomplete) vs - [x] (complete)
• Count complete vs total tasks
• If incomplete tasks exist:
  • Add CRITICAL issue for each incomplete task
  • Recommendation: "Complete task: <description>" or "Mark as done if already implemented"

Spec Coverage:

• If delta specs exist in openspec/changes/<name>/specs/:
  • Extract all requirements (marked with "### Requirement:")
  • For each requirement:
    • Search codebase for keywords related to the requirement
    • Assess if implementation likely exists
  • If requirements appear unimplemented:
    • Add CRITICAL issue: "Requirement not found: <requirement name>"
    • Recommendation: "Implement requirement X: <description>"

Verify Correctness

Requirement Implementation Mapping:

• For each requirement from delta specs:
  • Search codebase for implementation evidence
  • If found, note file paths and line ranges
  • Assess if implementation matches requirement intent
  • If divergence detected:
    • Add WARNING: "Implementation may diverge from spec: <details>"
    • Recommendation: "Review <file>:<lines> against requirement X"

Scenario Coverage:

• For each scenario in delta specs (marked with "#### Scenario:"):
  • Check if conditions are handled in code
  • Check if tests exist covering the scenario
  • If scenario appears uncovered:
    • Add WARNING: "Scenario not covered: <scenario name>"
    • Recommendation: "Add test or implementation for scenario: <description>"

Verify Coherence

Design Adherence:

• If design.md exists in contextFiles:
  • Extract key decisions (look for sections like "Decision:", "Approach:", "Architecture:")
  • Verify implementation follows those decisions
  • If contradiction detected:
    • Add WARNING: "Design decision not followed: <decision>"
    • Recommendation: "Update implementation or revise design.md to match reality"
• If no design.md: Skip design adherence check, note "No design.md to verify against"

Code Pattern Consistency:

• Review new code for consistency with project patterns
• Check file naming, directory structure, coding style
• If significant deviations found:
  • Add SUGGESTION: "Code pattern deviation: <details>"
  • Recommendation: "Consider following project pattern: <example>"

Generate Verification Report

Summary Scorecard:

## Verification Report: <change-name>

### Summary
| Dimension    | Status           |
|--------------|------------------|
| Completeness | X/Y tasks, N reqs|
| Correctness  | M/N reqs covered |
| Coherence    | Followed/Issues  |

Issues by Priority:

1. CRITICAL (Must fix before archive):

   • Incomplete tasks
   • Missing requirement implementations
   • Each with specific, actionable recommendation

2. WARNING (Should fix):

   • Spec/design divergences
   • Missing scenario coverage
   • Each with specific recommendation

3. SUGGESTION (Nice to fix):

   • Pattern inconsistencies
   • Minor improvements
   • Each with specific recommendation

Final Assessment:

• If CRITICAL issues: "X critical issue(s) found. Fix before archiving."
• If only warnings: "No critical issues. Y warning(s) to consider. Ready for archive (with noted improvements)."
• If all clear: "All checks passed. Ready for archive."