openspec-verify-change

Verify an OpenSpec change implementation against its specs, tasks, and design.

3|Updated Nov 25, 2025
One-click install
npx skills add https://github.com/g1331/AutoRouter --skill openspec-verify-change-g1331
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-verify-change
Source: https://github.com/g1331/AutoRouter/tree/main/.claude/skills/openspec-verify-change
Command: npx skills add https://github.com/g1331/AutoRouter --skill openspec-verify-change-g1331

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Verify that an implementation matches the change artifacts (specs, tasks, design) and is ready for archiving.

Core Features & Use Cases

  • Completeness checks across task completion and delta specs
  • Correctness assessment mapping requirements to code and scenarios
  • Coherence evaluation against design decisions and code patterns
  • Use Case: QA and archival verification for change-driven development.

Quick Start

Provide a change name and run the verification workflow to generate a comprehensive report.

Frequently Asked Questions about openspec-verify-change

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What is change verification in spec-driven development?

Change verification identifies whether an implementation fulfills its specs, tasks, and design by evaluating completeness, correctness, and coherence. It maps requirements to code and checks scenario coverage before archiving.

How do I verify implementation completeness against delta specs and tasks?

You verify implementation completeness by providing a change name and running the verification workflow. This checks task completion against delta specs and generates a structured report with prioritized CRITICAL, WARNING, and SUGGESTION issues.

Can I check if my code matches design decisions and coherence patterns?

Yes, you can check code coherence by evaluating the implementation against established design decisions and code patterns. The verification process assesses design adherence to ensure the change matches documented design notes.

Does change verification work for archiving workflows without external dependencies?

Yes, change verification operates without external dependencies by analyzing change artifacts directly. It requires delta specs, tasks artifacts, and potential design notes to guide the verification process and generate an archival readiness report.

What issues are identified when an implementation fails requirement mapping?

When an implementation fails requirement mapping, the verification identifies issues categorized as CRITICAL, WARNING, or SUGGESTION. These prioritized findings highlight specific gaps in scenario coverage, correctness, and design adherence.