openspec-verify-change

Verify implementation alignment with OpenSpec change artifacts and generate a report.

2|1|Updated Mar 16, 2026

Search Tags:#automation #validation #quality-assurance #openspec #code-review #specs #change-verification

Ready to run

npx skills add https://github.com/Yi-ming-Zhao/Fittin --skill openspec-verify-change-yi-ming-zhao

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: openspec-verify-change
Source: https://github.com/Yi-ming-Zhao/Fittin/tree/main/.cursor/skills/openspec-verify-change
Command: npx skills add https://github.com/Yi-ming-Zhao/Fittin --skill openspec-verify-change-yi-ming-zhao

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This step helps teams verify that an implementation matches the OpenSpec change artifacts (specs, tasks, and design decisions), preventing misalignment before archiving.

Core Features & Use Cases

Completeness checks of task completion and delta-spec coverage.
Correctness checks of requirement implementation mapping and scenario coverage.
Coherence checks for design adherence and code pattern consistency.
Use Case: A developer runs the verification after implementing a change to confirm alignment with specs and to surface gaps before merging.

Quick Start

Provide the change name to verify, and let OpenSpec guide the verification workflow to generate a report.

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 implementation against OpenSpec change artifacts?▼

To verify code implementation against OpenSpec change artifacts, you provide the change name and the workflow generates a report checking completeness, correctness, and coherence. This surfaces gaps to prevent misalignment before archiving or merging.

What does delta-spec verification check for in a change workflow?▼

Delta-spec verification checks for task completion coverage, requirement implementation mapping, and scenario coverage. It ensures the implementation matches the OpenSpec design decisions and specs with actionable recommendations.

How do I check if my code matches design decisions before merging?▼

You check if code matches design decisions before merging by running a coherence verification that validates design adherence and code pattern consistency. This confirms alignment with OpenSpec specs and tasks to surface any gaps.

Can I use automated validation for task completion checks in OpenSpec?▼

Yes, you can use automated validation for task completion checks in OpenSpec. The verification workflow evaluates completeness of delta-spec coverage and task completion, applying actionable recommendations to correct any misalignment.

When do I need to run change verification in my software engineering workflow?▼

You need to run change verification after implementing a change and before archiving or merging. It confirms alignment with OpenSpec artifacts, preventing spec misalignment and surfacing gaps in requirement mapping or design coherence.

What is the best way to surface gaps in requirement implementation mapping?▼

The best way to surface gaps in requirement implementation mapping is through a correctness verification check. This evaluates how well the implementation maps to OpenSpec requirements and scenario coverage, generating a report with actionable recommendations.