openspec-verify-change

Verify implementation alignment with delta specs, tasks, and design artifacts.

1|Updated Mar 10, 2026

Search Tags:#spec-driven #verification #code-quality #openspec #change-artifacts

Ready to run

npx skills add https://github.com/woutervanranst/Arius7 --skill openspec-verify-change-woutervanranst

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: openspec-verify-change
Source: https://github.com/woutervanranst/Arius7/tree/main/.opencode/skills/openspec-verify-change
Command: npx skills add https://github.com/woutervanranst/Arius7 --skill openspec-verify-change-woutervanranst

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill validates that an implementation conforms to the defined change artifacts (specs, tasks, and design) to ensure completeness, correctness, and coherence before archiving.

Core Features & Use Cases

Delta spec alignment: checks that the implementation matches the delta specs for a given change.
Artifact-driven verification: analyzes tasks, specs, scenarios, and design to surface gaps.
Guided remediation: produces actionable recommendations and references for fixes.

Quick Start

Run openspec verify-change for a given change to start the verification pass.

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 my code implementation matches delta specs and design artifacts?▼

To verify implementation matches delta specs, run a verification pass that parses change artifacts, maps requirements to code, assesses scenario coverage, and checks for design deviations to ensure completeness and correctness.

What does spec-driven verification check when validating a code change?▼

Spec-driven verification checks that your implementation aligns with delta specs, tasks, and design artifacts by assessing completeness, correctness, and coherence, then generates a structured verification report with actionable remediation references.

How do I map requirements to code to detect design deviations in a change?▼

You can map requirements to code by loading change artifacts and delta specs, which allows the verification process to detect design deviations and surface gaps between the defined scenarios and the actual implementation.

Can I use artifact-driven verification for changes with only delta specs and no full design?▼

Artifact-driven verification applies to changes with delta specs and associated artifacts, supporting status checks and artifact loading to assess scenario coverage and generate a structured report even with limited design documents.

What is the best way to generate a structured verification report before archiving a change?▼

The best way to generate a structured verification report before archiving is to run a verification pass that analyzes tasks, specs, scenarios, and design artifacts to surface gaps and produce actionable recommendations for fixes.