openspec-verify-change

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

1|Updated Apr 9, 2026
One-click install
npx skills add https://github.com/CoderCoco-Studios/Hyveon --skill openspec-verify-change-codercoco-studios
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-verify-change
Source: https://github.com/CoderCoco-Studios/Hyveon/tree/main/.claude/skills/openspec-verify-change
Command: npx skills add https://github.com/CoderCoco-Studios/Hyveon --skill openspec-verify-change-codercoco-studios

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: Assesses 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 checks based on available artifacts, verifying only tasks when 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 implementation evidence, and the design decisions were followed before archiving the change. ## Quick Start Ask the assistant to verify that the implementation of your current 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 openspec CLI: it reads the change's tasks, specs, and design artifacts, then checks task completion, requirement implementation, and design adherence. The output is a report with CRITICAL, WARNING, and SUGGESTION issues.

What does the OpenSpec verification report check?

The report 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 openspec CLI is required. The workflow runs commands like openspec status, openspec instructions apply, and openspec list to discover changes and load artifact file paths.

What happens if a change has no design document?

The verification degrades gracefully. If only tasks exist, it verifies task completion only; if tasks and specs exist, it checks completeness and correctness; design adherence checks are skipped and noted when no design.md is present.

How are verification issues prioritized?

Issues are grouped into CRITICAL (incomplete tasks, missing requirement implementations), WARNING (spec or design divergences, uncovered scenarios), and SUGGESTION (pattern inconsistencies). When uncertain, the workflow prefers lower severity to avoid false positives.