openspec-verify-change

Verifying OpenSpec changes before archiving requires checking that delta specs in openspec/changes/<name>/specs are fully implemented. The process validates completeness, correctness, and coherence across code, tests, and documentation, producing a report with CRITICAL, WARNING, and SUGGESTION issues.

OpenSpec change verification is the process of validating that an implementation matches its change artifacts. You need it before archiving changes to ensure specs, tasks, and design documents are fully and correctly implemented without missing requirements.

Checking delta spec completeness involves mapping requirements from delta specs to your code changes and test coverage. This ensures every requirement in the OpenSpec change artifacts has a corresponding implementation and validates correctness.

You can validate design coherence by assessing design decisions and pattern consistency across the implementation. The skill reviews context files like design.md alongside code and tests to verify coherence before archiving.

Running OpenSpec change validation requires access to delta specs located in openspec/changes/<name>/specs, along with context files like tasks.md and design.md. These artifacts provide the requirements and design decisions to verify against.

In a change verification report, CRITICAL issues indicate severe failures in matching implementation to specs, while WARNING issues highlight potential inconsistencies. SUGGESTION issues provide recommendations for improving coherence and completeness before archiving.