openspec-verify-change

Verify implementation completeness, correctness, and coherence against OpenSpec change artifacts.

Updated Sep 16, 2026
One-click install
npx skills add https://github.com/JoeShi/coding-agent-usage-montior --skill openspec-verify-change-joeshi
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-verify-change
Source: https://github.com/JoeShi/coding-agent-usage-montior/tree/main/.kimi-code/skills/openspec-verify-change
Command: npx skills add https://github.com/JoeShi/coding-agent-usage-montior --skill openspec-verify-change-joeshi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Before archiving an OpenSpec change, teams need confidence that the implementation actually matches the planned specs, tasks, and design decisions. This Skill automates that audit by cross-checking code against change artifacts and producing a structured verification report. ## Core Features & Use Cases - Three-Dimension Verification: Checks Completeness (task checkboxes, spec coverage), Correctness (requirement implementation, scenario coverage), and Coherence (design adherence, code pattern consistency). - Prioritized Issue Report: Generates a markdown scorecard grouping findings into CRITICAL, WARNING, and SUGGESTION issues, each with actionable recommendations and file references. - Graceful Degradation: Adapts verification depth based on available artifacts, verifying only tasks when specs or design docs are missing. - Use Case: After finishing implementation of a spec-driven change, run this Skill to confirm all tasks are checked off, every requirement has corresponding code, and the design decisions were followed before archiving the change. ## Quick Start Ask the assistant to verify that the implementation of a specific OpenSpec change matches its specs, tasks, and design before archiving.

Frequently Asked Questions about openspec-verify-change

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I verify an OpenSpec change before archiving?

Run the verification workflow with the change name, and it checks task completion, requirement implementation, and design adherence. It outputs a report with CRITICAL, WARNING, and SUGGESTION issues so you know whether the change is ready to archive.

What does the openspec verify workflow check?

It 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).

Does openspec-verify-change require the openspec CLI?

Yes, the workflow depends on the openspec CLI to run commands like status, instructions, and list for reading change artifacts. Without the CLI installed, the verification steps cannot retrieve change context.

What happens if a change has no design document?

The verification degrades gracefully: with only tasks it checks completion, with tasks plus specs it checks completeness and correctness, and the design adherence check is skipped with a note explaining why.

How are verification issues prioritized in the report?

Issues are grouped into CRITICAL (incomplete tasks, missing requirement implementations), WARNING (spec or design divergences, uncovered scenarios), and SUGGESTION (pattern inconsistencies). Each issue includes a specific actionable recommendation.