openspec-verify-change

Verify implementation matches OpenSpec change artifacts before archiving.

Updated Apr 7, 2026
One-click install
npx skills add https://github.com/zh-impact/agent-feeder --skill openspec-verify-change-zh-impact
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-verify-change
Source: https://github.com/zh-impact/agent-feeder/tree/main/.claude/skills/openspec-verify-change
Command: npx skills add https://github.com/zh-impact/agent-feeder --skill openspec-verify-change-zh-impact

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Before archiving a change in an OpenSpec workflow, 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: Assesses Completeness (task checkboxes, spec coverage), Correctness (requirement implementation, scenario coverage), and Coherence (design adherence, code pattern consistency). - Prioritized Issue Reporting: Groups findings into CRITICAL, WARNING, and SUGGESTION levels, each with specific actionable recommendations and file/line references. - Graceful Degradation: Adapts verification depth based on available artifacts, verifying only tasks if specs or design docs are missing. - Use Case: After finishing a feature tracked by an OpenSpec change, run verification to confirm all tasks are checked off, every requirement has corresponding code, and the implementation follows the design before archiving the change. ## Quick Start Verify that my current OpenSpec change implementation is complete and ready to archive.

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 a change name, or let it prompt you to select from available changes via openspec list. It checks task completion, requirement implementation, and design adherence, then outputs a report telling you whether the change is ready to archive.

What does the OpenSpec verification report check?▼

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

Does openspec-verify-change work without a design.md file?▼

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 checks are skipped and noted when design.md is absent.

What happens if I don't specify a change name?▼

The skill runs openspec list --json and prompts you to select a change using an interactive question. It never auto-selects or guesses a change, and marks changes with incomplete tasks as In Progress.

What are the limitations of automated spec verification?▼

Verification relies on keyword searches and reasonable inference rather than perfect certainty, so false positives are possible. The skill mitigates this by preferring lower severity levels when uncertain, but manual review of flagged divergences is still recommended.