openspec-verify-change

Verify implementation matches OpenSpec change artifacts before archiving.

4|Updated May 13, 2026
One-click install
npx skills add https://github.com/RuixeWolf/modbus-simulator --skill openspec-verify-change-ruixewolf
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-verify-change
Source: https://github.com/RuixeWolf/modbus-simulator/tree/main/.opencode/skills/openspec-verify-change
Command: npx skills add https://github.com/RuixeWolf/modbus-simulator --skill openspec-verify-change-ruixewolf

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When working with spec-driven development, it is easy for code to drift away from the tasks, requirements, and design decisions recorded in change artifacts. This Skill audits an implementation against its OpenSpec change artifacts so gaps are caught before the change is archived. ## 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). - Structured Report: Produces a markdown verification report with a summary scorecard and issues grouped as CRITICAL, WARNING, or SUGGESTION, each with actionable recommendations and file references. - Graceful Degradation: Adapts checks based on which artifacts exist (tasks only, tasks plus specs, or full artifacts including design). - Use Case: Before archiving a spec-driven change, run the verification to confirm all tasks are checked off, every requirement has implementation evidence, and the code follows the recorded design decisions. ## 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, which loads the change's tasks, specs, and design artifacts via the openspec CLI, then checks task completion, requirement implementation, and design adherence. It outputs a report telling you whether the change is ready to archive.

What does the OpenSpec verification report check?▼

The report checks three dimensions: completeness (checkbox tasks and spec requirement coverage), correctness (implementation evidence and scenario coverage), and coherence (design decision adherence and code pattern consistency). Issues are grouped as CRITICAL, WARNING, or SUGGESTION.

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

Yes, the Skill requires the openspec CLI to be installed. It runs commands like openspec status, openspec instructions apply, and openspec list to discover changes and load artifact file paths.

What happens if a change only has a tasks file?▼

The verification degrades gracefully. With only tasks.md it verifies task completion only; with tasks plus specs it also checks correctness; with full artifacts including design.md it verifies all three dimensions, noting which checks were skipped.

How do I verify a change in a specific OpenSpec store?▼

Name the store and the workflow runs openspec store list --json to discover registered store ids, then appends --store <id> to subsequent openspec commands. The store selection stays sticky for the rest of the verification workflow.