openspec-verify-change

Spec verification checks that your implementation matches change artifacts by validating task completeness, requirement coverage, and scenario correctness before archiving. It generates a prioritized report highlighting CRITICAL, WARNING, and SUGGESTION issues with specific next steps.

A code-to-spec audit checks requirement-to-code evidence, scenario coverage, and adherence to design decisions. It assesses whether declared requirements appear implemented and verifies that task checkboxes are marked complete to ensure coherence across the change artifacts.

Requirement coverage and task completeness are checked by enumerating artifacts using list, status, and instructions apply commands. This process verifies that task checkboxes are complete and declared requirements are reflected in the codebase before the change is archived.

Scenario testing or requirement coverage checks fail when the codebase does not fully reflect the delta specs and design decisions. The verification output identifies these gaps as CRITICAL or WARNING issues, providing specific next steps to align the implementation with the change artifacts.

Yes, spec validation safely prompts you to choose a specific change when the name is missing or ambiguous. This ensures the verification report accurately targets the correct change artifacts, tasks, and delta specs before proceeding with the audit.

Spec verification is needed when preparing to archive an openspec change. It ensures your current branch's implementation fully satisfies the selected change's specs, tasks, and design decisions, preventing incomplete or incorrect work from being archived.