openspec-verify-change

Validate OpenSpec delta implementations against specs, tasks, and design artifacts.

Updated Apr 6, 2026
One-click install
npx skills add https://github.com/ybenitezf/pi-github --skill openspec-verify-change-ybenitezf
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-verify-change
Source: https://github.com/ybenitezf/pi-github/tree/main/.opencode/skills/openspec-verify-change
Command: npx skills add https://github.com/ybenitezf/pi-github --skill openspec-verify-change-ybenitezf

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Verifies that a change's implementation aligns with its change artifacts (specs, tasks, and design) to ensure completeness, correctness, and coherence before archiving.

Core Features & Use Cases

  • Completeness checks for task completion and delta-spec coverage.
  • Correctness assessment by mapping requirements to code and evaluating scenario coverage.
  • Coherence evaluation against design decisions and code patterns.

Quick Start

Invoke the openspec-verify-change workflow to generate a verification report for the selected change.

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 a code change matches its specs before archiving?

Spec coverage checks validate that delta-specs fully describe the implemented change by mapping requirements to code, evaluating scenario coverage, and identifying gaps between the written specifications and the actual delta changes produced by OpenSpec.

What does artifact validation check for in a software change?

Artifact validation checks task completeness, spec coverage, and design coherence across eligible artifacts, mapping requirements to code and evaluating whether the implementation aligns with design decisions and code patterns before archiving.

How do I check task completeness for delta changes in OpenSpec?

Check task completeness for delta changes by recalculating whether each task is completed and mapping the implementation back to the change artifacts, ensuring all specs, tasks, and design elements are accounted for before archiving.

Can I assess design coherence and code pattern alignment automatically?

Yes, design coherence is assessed automatically by evaluating the implementation against documented design decisions and code patterns, reporting findings with actionable recommendations and file references for any identified gaps.

When should I run a verification report on my change implementation?

Run a verification report on your change implementation right before archiving to identify gaps in task completion, spec coverage, and design coherence, ensuring the delta changes are fully correct and complete.