openspec-verify-change

Name: openspec-verify-change
Availability: InStock
Author: zdpk

Verify implementation matches delta specs and tasks before archiving.

Updated Jan 23, 2026

Search Tags:#verification #openspec #code-review #artifact #spec-validation #change-management #delta-specs

Ready to run

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

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This section explains that it helps teams validate that a change's implementation matches delta specs and tasks before archiving.

Core Features & Use Cases

Validate delta-spec alignment by comparing implemented changes against defined requirements.
Map each requirement to its code change and associated tasks, generating traceability.
Generate a structured verification report that highlights gaps, coverage, and risk for archive decisions.
Use cases include pre-archive validation during release cycles, code reviews for large changes, and governance checks for compliance.

Quick Start

Run openspec status for the target change and review the resulting verification 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 changes match delta specs before archiving?▼

To verify code changes match delta specs before archiving, you can validate delta-spec alignment by comparing implemented changes against defined requirements, mapping each requirement to its code change, and generating a structured verification report highlighting gaps and coverage.

What is delta spec validation in change management?▼

Delta spec validation in change management is the process of checking that a change's implementation matches its specifications, tasks, and design. It ensures delta specs exist, maps requirements to code, and checks task completion before archiving.

Can I use spec validation for code reviews on large changes?▼

Yes, you can use spec validation for code reviews on large changes. It maps each requirement to its associated code changes and tasks, generating traceability and a structured verification report that highlights gaps, coverage, and risk for archive decisions.

How do I generate a traceability report for requirement mapping?▼

You generate a traceability report for requirement mapping by mapping each requirement to its code change and associated tasks. This process produces a structured verification report highlighting gaps, coverage, and risk for governance checks and archive decisions.

Does openspec-verify-change work for compliance governance checks?▼

Yes, openspec-verify-change works for compliance governance checks. It validates that a change's implementation matches delta specs and tasks before archiving, generating a structured verification report that highlights gaps, coverage, and risk for release cycles.

What's the best way to check task completion before archiving a change?▼

The best way to check task completion before archiving a change is to run a validation process that ensures delta specs exist, maps requirements to code, and generates a structured verification report highlighting gaps, coverage, and risk for archive decisions.