openspec-verify-change

Verify implementation matches OpenSpec change artifacts before archiving.

3|1|Updated Apr 29, 2026
One-click install
npx skills add https://github.com/firstsun-dev/skills --skill openspec-verify-change-firstsun-dev
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-verify-change
Source: https://github.com/firstsun-dev/skills/tree/main/plugins/spec-driven-development/skills/openspec-verify-change
Command: npx skills add https://github.com/firstsun-dev/skills --skill openspec-verify-change-firstsun-dev

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. This Skill automates that audit by checking completeness, correctness, and coherence against the change artifacts. ## 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 available artifacts, verifying only tasks if that is all that exists, and noting skipped checks. - Use Case: After finishing implementation of a spec-driven change, run the verification 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 agent to verify that the implementation of the 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 issues grouped by severity.

What does the OpenSpec verification report check?▼

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

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

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

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

The skill degrades gracefully: with only tasks.md it verifies task completion only, with tasks plus specs it checks completeness and correctness, and with full artifacts it verifies all three dimensions. Skipped checks are always noted.

How are verification issues prioritized in the report?▼

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