openspec-verify-change

Compare implemented code against change artifacts to verify compliance.

Updated Feb 15, 2026
One-click install
npx skills add https://github.com/mazhewitt/budget-analyser --skill openspec-verify-change-mazhewitt
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-verify-change
Source: https://github.com/mazhewitt/budget-analyser/tree/main/.gemini/skills/openspec-verify-change
Command: npx skills add https://github.com/mazhewitt/budget-analyser --skill openspec-verify-change-mazhewitt

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill ensures that a given implementation matches the defined change artifacts (specs, tasks, and design) to prevent archiving incomplete work.

Core Features & Use Cases

  • Delta-spec verification: Compare code against delta specs to confirm coverage.
  • Artifact alignment: Validate that tasks, specs, and design artifacts are consistent.
  • Pre-archive validation: Ensure completeness before archiving changes.

Quick Start

Verify the selected change against its artifacts by running the openspec 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 my code implementation matches change artifacts before archiving?

Delta spec verification compares implemented code against delta specs, tasks, and design artifacts to identify coverage gaps and ensure verifiable compliance before archiving incomplete work.

What is change artifact alignment and how does it validate code completeness?

Change artifact alignment validates that tasks, specs, and design artifacts are mutually consistent and match implemented code, producing a structured verification result with completeness, correctness, and coherence assessments plus actionable recommendations.

How do I check if delta specs match implemented code for pre-archive validation?

Pre-archive validation checks delta specs against implemented code by defining the validation scope, identifying gaps between code and defined change artifacts, and producing a structured verification report with actionable recommendations.

What does a verification report include when checking code against specs and design artifacts?

A verification report includes structured results containing completeness, correctness, and coherence assessments that identify gaps between implemented code and defined change artifacts, alongside actionable recommendations for resolution.

Can I validate task consistency across specs and design artifacts without manual review?

Yes, artifact alignment validation automatically checks consistency across tasks, specs, and design artifacts against implemented code to produce structured verification results with completeness, correctness, and coherence assessments without requiring manual cross-referencing.

Why does code review against change artifacts prevent archiving incomplete work?

Code review against change artifacts prevents archiving incomplete work by identifying gaps between implemented code and defined specs, tasks, and design documents before changes are archived, ensuring verifiable compliance through structured verification.