openspec-verify-change

Verify implementation against change artifacts and generate a prioritized gap report.

Updated Apr 3, 2026

Search Tags:#verification #task tracking #openspec #spec validation #design adherence #change review

Ready to run

npx skills add https://github.com/sachinnair90/gitgloss --skill openspec-verify-change-sachinnair90

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you confirm that an implementation fully matches its planned change artifacts before the work is archived, reducing the risk of shipping incomplete or inconsistent changes.

Core Features & Use Cases

Task Completion Review: Checks task checkboxes to identify unfinished work that must still be implemented.
Requirement Coverage Review: Compares delta specs against the codebase to find missing or partially implemented requirements.
Scenario and Design Validation: Reviews scenario coverage and design adherence to surface divergence between intent and implementation.
Use Case: Use this Skill when a feature branch is ready for review and you need a structured verification report that highlights critical gaps, warnings, and suggestions.

Quick Start

Ask the skill to verify the named change against its tasks, specs, and design artifacts and return a prioritized report of any gaps or inconsistencies.

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 implementation against change artifacts before archiving a feature branch?▼

To verify implementation against change artifacts, you can generate a prioritized verification report that checks task completion, requirement coverage, and design adherence to surface any inconsistencies before archiving. The report highlights critical gaps, warnings, and suggestions.

What is spec-driven change validation and how does it work?▼

Spec-driven change validation compares delta specs and task checkboxes against the codebase to find missing or partially implemented requirements. It checks scenario coverage and design adherence to surface divergence between the planned intent and the actual implementation before archiving.

How do I check requirement coverage and task completion for a spec-driven project?▼

Requirement coverage and task completion checks compare your delta specs and task checkboxes against the codebase to identify unfinished work and missing requirements. This process yields a prioritized report highlighting critical gaps, warnings, and suggestions for incomplete implementations.

Do I need the openspec CLI to review scenario coverage and design adherence?▼

Yes, reviewing scenario coverage and design adherence requires openspec CLI access. The CLI is used to list changes, inspect status, load context files, and generate the prioritized verification report that surfaces divergences between your design intent and implementation.

What is the best way to surface completion gaps before archiving code changes?▼

The best way to surface completion gaps before archiving is to run a structured change validation review. This checks task checkboxes, compares delta specs against the codebase, and validates scenario coverage to generate a prioritized report of critical gaps and warnings.

Why does my implementation diverge from the planned design artifacts during change review?▼

Implementation diverges from planned design artifacts when scenario coverage and design adherence checks surface inconsistencies between the delta specs and the codebase. A structured change validation report identifies these specific critical gaps, warnings, and missing requirements.