openspec-verify-change

Run the verification workflow with a change name, or let it prompt you to select from available changes via openspec list. It checks task completion, requirement coverage, and design adherence, then outputs a report telling you whether the change is ready to archive.

The report checks three dimensions: Completeness (task checkboxes and spec requirement coverage), Correctness (implementation evidence and scenario coverage), and Coherence (design decision adherence and code pattern consistency). Issues are grouped as CRITICAL, WARNING, or SUGGESTION.

Yes, it degrades gracefully based on available artifacts. With only tasks.md it verifies task completion; with tasks and specs it checks completeness and correctness; design adherence is only verified when design.md exists, and skipped checks are noted.

You need the openspec CLI installed and a project using OpenSpec change artifacts under openspec/changes. The skill runs commands like openspec list, openspec status, and openspec instructions apply to load the change context.

Correctness checks use keyword search and reasonable inference rather than exact proof, so uncertainty can occur. The skill mitigates this by preferring SUGGESTION over WARNING and WARNING over CRITICAL when evidence is ambiguous.