openspec-verify-change

Verify implementation matches OpenSpec change artifacts before archiving.

Updated Feb 16, 2026
One-click install
npx skills add https://github.com/GQAdonis/artifact-refiner-skill --skill openspec-verify-change-gqadonis
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-verify-change
Source: https://github.com/GQAdonis/artifact-refiner-skill/tree/main/.kimi-code/skills/openspec-verify-change
Command: npx skills add https://github.com/GQAdonis/artifact-refiner-skill --skill openspec-verify-change-gqadonis

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Before archiving a change, teams need confidence that the implementation actually matches the planned specs, tasks, and design. This Skill automates that verification by cross-checking code against OpenSpec change artifacts and producing a structured report. ## Core Features & Use Cases - Three-Dimension Verification: Checks completeness (task and spec coverage), correctness (requirement implementation and scenario coverage), and coherence (design adherence and code pattern consistency). - Prioritized Issue Reporting: Generates a markdown report 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 documents 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 produces a report with CRITICAL, WARNING, and SUGGESTION issues plus a final readiness assessment.

What does the openspec verify workflow check?▼

It checks three dimensions: completeness (checkbox tasks and spec requirement coverage), correctness (requirement-to-code mapping and scenario coverage), and coherence (design decision adherence and code pattern consistency).

Does openspec-verify-change require the openspec CLI?▼

Yes, the openspec CLI is required. The workflow runs commands like openspec status, openspec instructions apply, and openspec list to discover changes and load artifact context files.

What happens if a change has no design document?▼

The verification degrades gracefully. With only tasks it checks task completion; with tasks and specs it checks completeness and correctness; design adherence checks are skipped and noted when no design.md exists.

Can I verify a change in a specific OpenSpec store?▼

Yes. Run openspec store list --json to discover registered store ids, then pass --store <id> on commands that read or write specs and changes. The flag stays sticky for the rest of the workflow.