openspec-verify-change

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

Updated Jul 23, 2026
One-click install
npx skills add https://github.com/shrek-abaper/sap-nexus-agent --skill openspec-verify-change-shrek-abaper
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-verify-change
Source: https://github.com/shrek-abaper/sap-nexus-agent/tree/main/.comet/skills/skills/openspec-verify-change
Command: npx skills add https://github.com/shrek-abaper/sap-nexus-agent --skill openspec-verify-change-shrek-abaper

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Before archiving a change, teams need confidence that the implementation actually matches the specs, tasks, and design decisions recorded in OpenSpec artifacts. This Skill automates that audit, producing a structured verification report instead of relying on manual cross-checking. ## 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 Report: Groups findings into CRITICAL, WARNING, and SUGGESTION levels, each with actionable recommendations and file/line references. - Graceful Degradation: Adapts checks based on which artifacts exist (tasks only, tasks plus specs, or full artifacts including design.md). - 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 code follows the recorded design decisions before archiving. ## Quick Start Ask the assistant to verify that the implementation of a specific 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 a change name, or let it prompt you to select from available changes via openspec list. It checks task completion, spec coverage, and design adherence, then outputs a report with CRITICAL, WARNING, and SUGGESTION issues.

What does the OpenSpec verification report contain?▼

The report contains a summary scorecard across Completeness, Correctness, and Coherence dimensions, plus grouped issues by priority. Each issue includes a specific, actionable recommendation with file and line references where applicable.

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.md file?▼

The verification degrades gracefully. With only tasks.md it checks task completion; with tasks and specs it adds correctness checks; design adherence is skipped and explicitly noted when design.md is absent.

When should I not rely on automated change verification?▼

Automated verification uses keyword search and reasonable inference, so it can produce false positives on requirement coverage. Treat WARNING and SUGGESTION items as review prompts rather than definitive proof of missing implementation.