openspec-verify-change

To verify code implementation matches design specs, you can run automated checks for completeness, correctness, and coherence against change artifacts. This process flags incomplete tasks, missing requirements, and spec divergences before merging or archiving.

Change verification in software engineering is the process of ensuring code implementations align with specified change artifacts, including specs, tasks, and design documents. It prevents drift and ensures quality by analyzing requirement coverage and design adherence.

To check for missing requirements and spec divergences before archiving, execute change verification commands to list and apply change instructions. This programmatically generates a verification report identifying incomplete tasks and code pattern inconsistencies.

Yes, you need openspec installed to verify requirement coverage and task completion. The Skill operates by executing the openspec CLI to list, status, and apply change instructions, then programmatically generating a verification report assessing coherence.

The best way to prevent drift between code and design documents is to perform automated verification that assesses completeness, correctness, and coherence. This ensures code implementations accurately reflect the intended design and specifications before archiving changes.

Your code implementation lacks coherence with defined change artifacts due to incomplete tasks, missing requirements, spec or design divergences, and code pattern inconsistencies. Running a verification check identifies these specific issues programmatically.