openspec-verify-change

Verify implementation completeness, correctness, and coherence against change artifacts.

1|Updated Mar 23, 2026
One-click install
npx skills add https://github.com/captaincontrat/audio-recap --skill openspec-verify-change-captaincontrat
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-verify-change
Source: https://github.com/captaincontrat/audio-recap/tree/main/.cursor/skills/openspec-verify-change
Command: npx skills add https://github.com/captaincontrat/audio-recap --skill openspec-verify-change-captaincontrat

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This verification skill ensures that an implementation matches the defined change artifacts (specs, tasks, and design), providing confidence before archiving.

Core Features & Use Cases

  • Completeness verification: checks that all required tasks are complete and that delta-spec requirements are addressed.
  • Correctness mapping: analyzes evidence in the codebase to determine alignment with the specified requirements and flags potential divergences.
  • Coherence checks: validates adherence to design decisions and coding patterns to maintain consistency across the change.
  • Use case: before finalizing a change, run the verifier to produce a report that highlights critical gaps and recommended remediations.

Quick Start

Run the verifier to validate the specified change against its delta specs and tasks.

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 against specs before archiving?

You verify code changes by analyzing the codebase against delta specs and tasks to evaluate completeness and correctness, generating a structured report with CRITICAL, WARNING, and SUGGESTION items.

What is delta spec verification in software engineering?

Delta spec verification checks that an implementation matches defined change artifacts, evaluating codebase completeness, correctness, and coherence to ensure alignment with specified requirements before archiving.

How do I check if all required tasks are complete in a code change?

You check task completeness by running a verification process that analyzes codebase evidence against delta-spec requirements, flags divergences, and produces a structured report with actionable remediation guidance.

Can I generate a code review report for change artifacts and design decisions?

Yes, you generate a verification report by validating implementation adherence to design decisions and coding patterns, outputting CRITICAL, WARNING, and SUGGESTION items with file references and recommended remediations.

What's the best way to evaluate codebase coherence during a change implementation?

Evaluate codebase coherence by validating adherence to design decisions and coding patterns, maintaining consistency across the change while mapping codebase evidence to specified requirements and flagging divergences.