openspec-verify-change

Verify implementation matches change specs, tasks, and design artifacts.

Updated Apr 20, 2020
One-click install
npx skills add https://github.com/UnterrainerInformatik/java-rdb-utils --skill openspec-verify-change-unterrainerinformatik
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-verify-change
Source: https://github.com/UnterrainerInformatik/java-rdb-utils/tree/main/.claude/skills/openspec-verify-change
Command: npx skills add https://github.com/UnterrainerInformatik/java-rdb-utils --skill openspec-verify-change-unterrainerinformatik

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Before archiving a change, teams need confidence that the implementation actually matches the planned specs, tasks, and design decisions. This Skill automates that validation by cross-checking code against change artifacts and producing a structured verification report. ## 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). - Prioritized Issue Reporting: Groups findings into CRITICAL, WARNING, and SUGGESTION levels with specific file and line references plus actionable recommendations. - Graceful Degradation: Adapts verification depth based on available artifacts, verifying only tasks if specs or design documents 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 the current change implementation against its specs and tasks using the openspec verify workflow.

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 coverage, and design adherence, then outputs a report with issues grouped by severity.

What does the openspec verify report check?▼

The report covers three dimensions: Completeness (task checkboxes and spec requirement coverage), Correctness (requirement implementation and scenario coverage in code), 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 list, openspec status, and openspec instructions apply to discover changes and load their artifact files.

What happens if a change has no design document?▼

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

Can openspec verify-change auto-select which change to check?▼

No, it never guesses or auto-selects a change. If no change name is provided, it lists available changes and asks the user to choose, marking changes with incomplete tasks as In Progress.