openspec-verify-change

Spec verification for change management systematically checks task completion, requirement coverage, and scenario coverage against OpenSpec change artifacts. It prevents incomplete or incorrect implementations from being archived by validating code matches delta specs and tasks.md.

Requirements traceability maps delta spec requirements and scenarios directly to implementation evidence. It validates design consistency and flags divergences from design decisions, ensuring your code changes align with the specified OpenSpec artifacts before archiving.

Check test coverage for OpenSpec changes by mapping scenarios from delta specs to implementation evidence. The verification process looks for proof of scenario coverage and highlights missing requirement implementations or divergences from design decisions.

Yes, openspec-verify-change supports schema-aware artifact loading via openspec status and instructions apply. It works with optional design.md and status schema metadata located alongside tasks.md and delta specs under openspec/changes/<name>/.

Your verification report flags missing requirement coverage because the system detects incomplete tasks from tasks.md and maps delta spec requirements to implementation evidence. It generates a prioritized completeness and correctness report highlighting these gaps.