openspec-verify-change

Spec verification checks that implementation artifacts align with recorded change specifications by validating task completion, spec requirement coverage, and scenario evidence. It uses openspec CLI commands to generate a structured report scoring completeness, correctness, and coherence.

Spec validation performs completeness, correctness, and coherence checks. It validates that checklist tasks are complete, detects mismatches between requirement intent and code evidence, flags missing test coverage, and verifies adherence to available design decisions.

You can check task completion by asking the verification process to inspect a specific change by name. It operates through openspec CLI commands for change listing and status inspection, parsing artifacts to report issues for archiving readiness.

Yes, openspec CLI is a required dependency. The verification process operates through its commands to apply artifacts, inspect change status, and generate the structured report that scores design adherence and requirement coverage.

You should run change verification before archiving a spec-driven change. It ensures all checklist tasks are marked complete, delta spec requirements are implemented, scenarios are covered by tests, and the codebase follows stated design decisions.

The best way is to run a correctness check that flags missing scenario and test coverage. It detects likely mismatches between requirement intent and code evidence by validating that each spec requirement has implementation proof.