openspec-verify-change

Verify implementation alignment with change artifacts using the openspec CLI.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/terry90918/horse-blessing-2026 --skill openspec-verify-change-terry90918
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-verify-change
Source: https://github.com/terry90918/horse-blessing-2026/tree/main/.claude/skills/openspec-verify-change
Command: npx skills add https://github.com/terry90918/horse-blessing-2026 --skill openspec-verify-change-terry90918

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Verify that an implementation matches the change artifacts (specs, tasks, design) to ensure completeness, correctness, and coherence before archiving.

Core Features & Use Cases

  • Validate alignment of implementation with delta specs, tasks artifacts, and design decisions.
  • Generate a structured verification report across Completeness, Correctness, and Coherence.
  • Interactively guide users to select a change name when not provided and load artifacts via the openspec CLI.

Quick Start

Run the verification workflow against the specified change to produce a comprehensive 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 my code implementation matches change specs before archiving?

Verifying code matches change specs requires inspecting delta specs, code, and tests via the openspec CLI to collect alignment evidence. This Skill generates a structured report evaluating completeness, correctness, and coherence across change artifacts.

What is spec review for code changes and when do I need it?

Spec review validates that implementations align with design decisions, task artifacts, and delta specs. You need this verification before archiving changes to ensure completeness, correctness, and coherence across your project artifacts.

How do I generate a verification report for change artifacts and code alignment?

Run the verification workflow against a specified change name to generate a report. It inspects delta specs, code, and tests via the openspec CLI, producing actionable recommendations based on completeness, correctness, and coherence findings.

Can I check implementation completeness if I don't specify a change name?

Yes, you can verify completeness without specifying a change name. The workflow interactively guides you to select a change name when not provided, then loads the necessary artifacts via the openspec CLI to perform the verification.

Does the openspec CLI support inspecting delta specs and tests for code review?

Yes, the openspec CLI supports inspecting delta specs, code, and tests for code review. The verification workflow uses it to load artifacts and collect evidence of alignment and gaps across the change for structured reporting.