openspec-verify-change

Name: openspec-verify-change
Availability: InStock
Author: yager-42

Validate implementation alignment with openspec delta specs and generate a structured verification report.

Updated Dec 26, 2025

Search Tags:#design #verification #tasks #openspec #specs #change-artifacts

Ready to run

npx skills add https://github.com/Yager-42/-- --skill openspec-verify-change-yager-42

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: openspec-verify-change
Source: https://github.com/Yager-42/--/tree/main/.codex/skills/openspec-verify-change
Command: npx skills add https://github.com/Yager-42/-- --skill openspec-verify-change-yager-42

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Verifies that an implementation matches the change artifacts (specs, tasks, and design) to ensure changes are complete, correct, and coherent before archiving.

Core Features & Use Cases

Validates the alignment between implemented code and delta specs, tasks, and design.
Generates a structured verification report across Completeness, Correctness, and Coherence.
Guides remediation by listing missing artifacts, potential divergences, and design-consistency issues.

Quick Start

Ask for a change name, load relevant artifacts with openspec, and generate a verification report before archiving.

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 matches change artifacts before archiving?▼

To verify implementation matches change artifacts, validate the alignment between your code and delta specs, tasks, and design. This generates a structured verification report detailing completeness, correctness, and coherence findings with concrete remediation recommendations.

What is the best way to check completeness and correctness across delta specs?▼

Checking completeness and correctness across delta specs involves applying the openspec workflow to retrieve change artifacts, inspect their presence, and assess coherence. This produces a structured report highlighting critical issues, warnings, and suggestions with file references.

How do I generate a verification report for missing artifacts and design divergences?▼

Generating a verification report for missing artifacts and divergences requires inspecting your target change against its specs and tasks. The process assesses completeness, correctness, and design-consistency to produce structured CRITICAL, WARNING, and SUGGESTION findings.

Can I use openspec to validate code alignment with tasks and design documents?▼

Yes, you can use openspec to validate code alignment with tasks and design documents. The workflow retrieves the relevant change artifacts, inspects their presence, and assesses whether the implementation is complete, correct, and coherent before archiving.

Why does my implementation diverge from the design specs and tasks?▼

Your implementation diverges from design specs and tasks due to missing artifacts, incorrect code alignment, or coherence issues across delta specs. A structured verification report identifies these specific divergences and provides concrete recommendations for remediation.