openspec-verify-change

Spec coverage mapping analyzes delta specs under openspec/changes/ to link documented requirements directly to code implementations and tests. It checks that every requirement in the change artifacts has corresponding code and test coverage.

To check if task checklists are complete for a code change, the skill reads change-context artifacts to parse task checkboxes and confirm their status. It validates that all tasks documented in the change specifications are marked as complete before archiving.

Yes, you can detect design inconsistencies by running design coherence checks. The skill compares your actual implementation against documented design decisions in the change artifacts to identify and report any deviations or incoherent logic.

The best way to generate an actionable verification report for spec validation is to assess design adherence and spec coverage comprehensively. The skill produces a report with clear CRITICAL, WARNING, and SUGGESTION items for any discovered issues.

Yes, you need openspec to validate delta changes because the skill specifically applies to delta changes produced by openspec. It extracts delta specs from the openspec directory structure to verify task completion and design coherence.