openspec-verify-change

Verifies code changes against openspec delta specs and tasks.

1|Updated Apr 13, 2026
One-click install
npx skills add https://github.com/MeetTechnology/AutoHire --skill openspec-verify-change-meettechnology
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-verify-change
Source: https://github.com/MeetTechnology/AutoHire/tree/main/.cursor/skills/openspec-verify-change
Command: npx skills add https://github.com/MeetTechnology/AutoHire --skill openspec-verify-change-meettechnology

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps ensure that a code change actually fulfills the associated specs, tasks, and design artifacts before archiving.

Core Features & Use Cases

  • Delta-spec verification: Load and compare delta specs from openspec against the implemented code and tests.
  • Artifact mapping: Analyze task checklists, scenarios, and design decisions to assess completeness and coherence.
  • Reporting: Generate a structured verification report with Completeness, Correctness, and Coherence.

Quick Start

Provide the change name and run the verification to ensure implementation matches the change artifacts.

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?

Spec verification validates implemented code against associated specs, tasks, and design artifacts. It loads delta specs, parses scenarios, and produces a structured report covering completeness, correctness, and coherence dimensions before archiving.

What is delta spec review and when do I need it?

Delta spec review compares spec changes from openspec against implemented code and tests. You need it during development workflows where changes must be verified against task checklists, scenarios, and design decisions before archiving.

How do I check if implementation mapping covers all scenarios?

Implementation mapping analyzes task checklists, scenarios, and design decisions to assess completeness and coherence. It loads delta specs, parses defined scenarios, and generates a verification report confirming scenario coverage.

Does openspec verification work without external dependencies?

Yes, openspec verification runs with no external dependencies. It supports loading delta specs directly, parsing tasks and scenarios, and producing a structured verification report with completeness, correctness, and coherence dimensions.

What's the best way to validate code correctness against change artifacts?

Validating code correctness requires loading change artifacts and comparing them against the implemented code. The verification process generates a structured report assessing completeness, correctness, and coherence across spec deltas, tasks, and scenarios.