openspec-verify-change

Verify software changes against delta artifacts for completeness, correctness, and coherence.

11|3|Updated Dec 20, 2025

Search Tags:#qa #verify #openspec #code-review #specs #artifact-validation #change-artifacts

Ready to run

npx skills add https://github.com/DarkHighness/coi-public --skill openspec-verify-change-darkhighness

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: openspec-verify-change
Source: https://github.com/DarkHighness/coi-public/tree/main/.gemini/skills/openspec-verify-change
Command: npx skills add https://github.com/DarkHighness/coi-public --skill openspec-verify-change-darkhighness

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams validate that a given software change is fully implemented and coherently aligned with the change artifacts (e.g., delta specs, tasks, and design guidance) before archiving.

Core Features & Use Cases

Completeness validation: verifies that all change artifacts (tasks.md, specs) are present and that the implementation matches the defined work items.
Correctness assessment: maps requirements to implementations, identifies divergences, and flags uncovered scenarios for remediation.
Coherence review: checks design adherence and code pattern consistency against project standards.
Output generation: builds a structured verification report with prioritized issues and actionable recommendations.

Quick Start

Provide the target change name to begin the verification workflow.

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 changes against delta specs before archiving?▼

You can verify code changes against delta specs by providing the target change name, which triggers a search of the codebase for specification alignment, scenario coverage, and design conformity before generating a structured verification report with actionable findings.

What is change artifact validation in software engineering?▼

Change artifact validation assesses software changes for Completeness, Correctness, and Coherence by mapping requirements to implementations, identifying divergences, and checking design adherence against project standards before archiving.

How do I check if my implementation matches tasks.md and design specs?▼

You can check if your implementation matches tasks.md and design specs through a validation workflow that verifies all change artifacts are present, maps defined work items to code, and flags uncovered scenarios for remediation.

Can I use this to assess code pattern consistency against project standards?▼

Yes, you can assess code pattern consistency using the Coherence review feature, which checks design adherence and verifies that the implementation patterns align with established project standards.

What is the best way to identify divergences between requirements and code?▼

The best way to identify divergences between requirements and code is to perform a Correctness assessment that maps requirements to implementations and flags uncovered scenarios for remediation.

Does the verification workflow work for changes with missing design documents?▼

Yes, the verification workflow applies to changes with varying levels of artifacts, including tasks.md and specs, so it can still validate Completeness and Correctness even when design documents are missing.