openspec-verify-change

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

Updated Jun 25, 2026
One-click install
npx skills add https://github.com/ismaelsoilet/ismaelsoilet-landing --skill openspec-verify-change-ismaelsoilet
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-verify-change
Source: https://github.com/ismaelsoilet/ismaelsoilet-landing/tree/main/.cursor/skills/openspec-verify-change
Command: npx skills add https://github.com/ismaelsoilet/ismaelsoilet-landing --skill openspec-verify-change-ismaelsoilet

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: Evaluates Completeness (task checkboxes, spec coverage), Correctness (requirement implementation, scenario coverage), and Coherence (design adherence, code pattern consistency). - Prioritized Issue Reporting: Generates a markdown report with a summary scorecard and issues grouped as CRITICAL, WARNING, or SUGGESTION, each with actionable recommendations and file references. - Graceful Degradation: Adapts verification depth based on available artifacts, from tasks-only checks to full spec and design validation. - 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 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 by selecting the change name, loading its artifacts via openspec status and openspec instructions, then checking tasks, specs, and design against the codebase. The result is a report with a go/no-go assessment for archiving.

What does the OpenSpec verification report check?▼

The report checks three dimensions: Completeness (task checkboxes and requirement coverage), Correctness (requirement implementation and scenario coverage), and Coherence (design adherence and code pattern consistency). Issues are grouped as CRITICAL, WARNING, or SUGGESTION.

Does openspec verify-change require the openspec CLI?▼

Yes, the openspec CLI is required. The workflow runs commands like openspec status, openspec instructions, and openspec list to discover changes and load artifact file paths before performing verification.

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

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

How are verification issues prioritized in the report?▼

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