openspec-verify-change

Verify an OpenSpec change implementation against its specs, tasks, and design.

45|3|Updated Jan 20, 2026
One-click install
npx skills add https://github.com/Charles5277/nuxt-supabase-starter --skill openspec-verify-change-charles5277
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-verify-change
Source: https://github.com/Charles5277/nuxt-supabase-starter/tree/main/.claude/skills/openspec-verify-change
Command: npx skills add https://github.com/Charles5277/nuxt-supabase-starter --skill openspec-verify-change-charles5277

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams verify that an implementation exactly matches the change artifacts (specs, tasks, design) before archiving, ensuring completeness and coherence of changes.

Core Features & Use Cases

  • Artifact-driven verification: automatically checks that delta specs align with code, tests, and design.
  • Multi-dimension quality: evaluates completeness, correctness, and coherence with actionable recommendations.
  • Use Case: when preparing a change for release, run this skill to confirm all required artifacts are implemented and consistent.

Quick Start

Provide the change name to start the verification process.

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 code implementations match OpenSpec change artifacts before archiving?

You verify change implementations by parsing openspec outputs and cross-referencing the codebase against specs, tasks, and design documents to generate a concise verification report with actionable remediation.

What is artifact-driven verification for delta changes across code and tests?

Artifact-driven verification checks that delta specs align with code, tests, and design by evaluating completeness, correctness, and coherence across the project to ensure coherent delivery before archiving.

How do I check if spec alignment is complete for a code release?

You check spec alignment by evaluating the implementation across multiple quality dimensions, confirming all required artifacts are implemented and consistent with the provided design and task specifications.

Do I need to provide a change name to start the artifact validation process?

Yes, you need to provide the specific change name to start the verification process, which allows the system to identify and cross-reference the associated artifacts within the project codebase.

What does change verification check for in a software engineering project?

Change verification checks for completeness, correctness, and coherence by applying artifact-driven validation to delta changes across code, tests, and documentation to ensure complete and coherent delivery.