openspec-verify-change

Verify implementation completeness against tasks and delta spec requirements.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you avoid archiving incomplete or inconsistent work by verifying that an implementation matches the change’s specs, tasks, and design artifacts.

Core Features & Use Cases

  • Change selection and status awareness: Lists available changes via the Openspec CLI and avoids guessing by prompting the user when the change name is missing or ambiguous.
  • Completeness verification: Checks task completion from tasks artifacts and validates requirement coverage from delta specs.
  • Correctness verification: Looks for evidence in the codebase that requirements and scenarios are implemented, and flags likely divergences.
  • Coherence verification: Compares implementation against design decisions when design.md is available to catch contradictions.

Quick Start

Use the openspec-verify-change skill to validate a selected change’s implementation against its tasks and spec requirements before archiving.

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 spec compliance for a codebase change before archiving?

Spec compliance verification checks task completeness, requirement coverage, and design coherence against change artifacts before archiving. It validates implementations by comparing delta specs and tasks.md files with actual codebase evidence to flag divergences.

What does pre-archive validation for spec-driven agent workflows involve?

Pre-archive validation involves loading change artifacts, checking task completion from tasks.md, validating requirement and scenario coverage from delta specs, and comparing implementations against design decisions to ensure structured reporting of critical, warning, and suggestion issues.

How do I check task coverage and requirement completeness for an Openspec change?

Task coverage and requirement completeness are checked by loading change artifacts via the Openspec CLI, verifying task completion status, and searching the codebase for evidence that requirements and scenarios from delta specs are actually implemented.

Can I validate design coherence against a design.md file during scenario testing?

Design coherence validation compares the implementation against design decisions when a design.md file is available. It catches contradictions between the codebase and the documented design decisions during the change verification process.

How do I select a specific change for verification when multiple changes exist?

Change selection lists available changes via the Openspec CLI and prompts the user when the change name is missing or ambiguous. This avoids guessing by requiring explicit user-selected change disambiguation before artifact loading begins.

What issue priorities are reported when implementation does not match change artifacts?

Structured reporting categorizes mismatches into critical, warning, and suggestion issue priorities. This highlights incomplete tasks, missing requirement coverage, and likely divergences found during codebase analysis to guide pre-archive corrections.