openspec-verify-change

Change verification validates that an implementation matches declared change artifacts for completeness, correctness, and coherence. It checks task completion, requirement coverage, and design adherence to produce a prioritized verification report before archiving.

Spec-driven change verification evaluates change sets containing tasks, delta specs, and design artifacts. It parses tasks.md and specs to check task completion and requirement-to-code mapping, generating prioritized CRITICAL, WARNING, and SUGGESTION issues.

Change verification supports graceful degradation when only some artifacts exist. It runs partial checks on available artifacts like tasks.md, reports which checks were skipped, and provides reasons for any skipped verification dimensions.

Change verification uses the openspec CLI to list available changes and requires explicit user selection to avoid guessing. After choosing a target change, it fetches change context and contextFiles to run the verification flow.

Change verification evaluates three dimensions: Completeness for task checklists and spec requirements, Correctness for requirement-to-code mapping and scenario coverage, and Coherence for design adherence and pattern consistency.

Change verification prevents premature archiving by checking implementation traceability from requirements to code. It produces an actionable report listing incomplete tasks, missing requirement implementations, and recommended fixes with file references before closing a change.