openspec-verify-change

To verify change implementations align with specs, you parse OpenSpec delta specs and task artifacts to compare the implementation against requirements, generating a structured report covering completeness, correctness, and coherence.

Artifact-driven verification compares a change's implementation directly against its OpenSpec delta specs, tasks, and design artifacts to ensure requirements are addressed and reports gaps before archiving.

You check if your codebase matches OpenSpec delta specs by loading the change context and running coherence checks that align design decisions and patterns with the implementation to report any gaps.

Yes, you can use OpenSpec instructions to validate changes before release by applying the command with a specific change name to load context, then reviewing the generated verification report for readiness.

A verification report for OpenSpec change artifacts includes comprehensive sections detailing completeness, correctness, and coherence, along with CRITICAL, WARNING, and SUGGESTION sections to determine archiving readiness.

You need to run a coherence check on your change artifacts when preparing for release to ensure that design decisions and patterns are fully aligned with the codebase and that all tasks are complete.