openspec-verify-change

To verify implementation matches specs and design before archiving, run a structured workflow that checks completeness, correctness, and coherence against your change artifacts. This generates a verification report with actionable recommendations to prevent archiving inconsistent changes.

Spec traceability checks whether delta specs align with code and all tasks are completed. You need to check it before archiving a change to ensure requirements are fully implemented and no design contradictions remain in your software project.

Yes, change verification checks design coherence to ensure design decisions are reflected in the implementation and validates task completion status. It produces a structured report confirming that requirements are implemented without design contradictions.

You generate a verification report by running the verification workflow for the target change. The report highlights completeness, correctness, and coherence checks, providing actionable recommendations to resolve any gaps between tasks, specs, and code.

The best way to validate code against change artifacts is to run an automated verification workflow that cross-references delta specs, tasks, and design decisions with the implementation, producing a structured report with actionable fix recommendations.

Archiving incomplete changes causes issues because unverified implementations may miss requirements or contain design contradictions. Change verification prevents this by validating alignment between artifacts and code, ensuring completeness and coherence before archival.