openspec-verify-change

Verify OpenSpec change implementations against specs, tasks, and design artifacts.

Updated Mar 31, 2026
One-click install
npx skills add https://github.com/cenmiao/openspec-pro --skill openspec-verify-change-cenmiao
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-verify-change
Source: https://github.com/cenmiao/openspec-pro/tree/main/.claude/skills/openspec-verify-change
Command: npx skills add https://github.com/cenmiao/openspec-pro --skill openspec-verify-change-cenmiao

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Verify that change implementations align with change artifacts to ensure completeness, correctness, and coherence before archiving.

Core Features & Use Cases

  • Automated change consistency checks across specs, tasks, and design artifacts.
  • Artifact loading and validation against delta specs to surface gaps.
  • Structured verification reporting with CRITICAL, WARNING, and SUGGESTION findings and actionable recommendations.

Quick Start

Provide the change name to begin validation, or prompt for available changes if omitted.

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 a change implementation matches its design artifacts before archiving?

Use automated consistency checks to validate code updates against delta specs and design artifacts. This surfaces gaps and ensures completeness, correctness, and coherence before archiving the change.

What is the best way to check completeness and correctness of delta specs in OpenSpec?

The best way to check delta specs coverage is by applying automated status checks and artifact loading to score completeness and correctness, generating a structured verification report with actionable recommendations.

How does change validation handle optional artifacts in OpenSpec projects?

Change validation handles optional artifacts by loading all available design artifacts and validating them against delta specs to surface any coverage gaps, ensuring coherence across the entire project before archiving.

Can I get actionable recommendations when validating changes across specs and tasks?

Yes, you can get actionable recommendations by running change validation. The process outputs a structured verification report with CRITICAL, WARNING, and SUGGESTION findings to guide fixes before archiving.

Do I need to provide a specific change name to start change validation?

You can provide a specific change name to begin validation immediately. If omitted, the validation process will prompt you to select from available changes in your OpenSpec project.

Why does my change verification report show CRITICAL findings during artifact loading?

Change verification reports show CRITICAL findings when automated status checks detect that change implementations do not align with change artifacts, indicating gaps in delta specs coverage or missing required design artifacts.