openspec-verify-change

Verify implementation matches change artifacts and emit a prioritized report.

5|Updated Apr 29, 2026

Search Tags:#verification #openspec #scenario testing #codebase scanning #design adherence #spec coverage #task auditing

Ready to run

npx skills add https://github.com/breuerfelix/spurwechsel --skill openspec-verify-change-breuerfelix

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: openspec-verify-change
Source: https://github.com/breuerfelix/spurwechsel/tree/main/.opencode/skills/openspec-verify-change
Command: npx skills add https://github.com/breuerfelix/spurwechsel --skill openspec-verify-change-breuerfelix

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents teams from archiving incomplete or incorrect implementations by systematically checking whether code and tasks actually match the change artifacts produced by the specification process.

Core Features & Use Cases

Completeness verification: Validates task checkboxes in tasks.md and flags any incomplete items as critical.
Spec and scenario coverage checks: Scans delta spec requirements and scenarios to detect missing or weak implementation evidence.
Coherence and design adherence: Compares implementation against design.md decisions when present and reports inconsistencies, while also noting pattern deviations.
Actionable verification output: Produces a structured report with CRITICAL, WARNING, and SUGGESTION items, including specific recommendations.

Quick Start

Ask the AI to verify the specified change, for example: Verify that the implementation matches the change artifacts for change "MyChange", and produce a readiness report for 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 my implementation matches spec-driven change artifacts before archiving?▼

Spec-driven development verification prevents archiving incomplete work by scanning change artifacts to check tasks, requirements, scenarios, and design coherence, then producing a prioritized readiness report with critical, warning, and suggestion items.

What is the best way to check task completeness in a spec-driven workflow?▼

Task completeness verification parses tasks.md artifacts to validate checkboxes and flags any incomplete items as critical issues in the final verification report.

How does scenario testing coverage check implementation against delta spec requirements?▼

Scenario testing coverage scans delta spec requirements and scenarios to detect missing or weak implementation evidence within the codebase.

Can I check design adherence by comparing implementation against design.md decisions?▼

Design adherence verification compares implementation code against design.md decisions when present, reporting inconsistencies and noting pattern deviations.

Do I need the openspec CLI to run queries for verifying change artifacts?▼

Yes, verifying change artifacts satisfies the requirements of running openspec CLI queries like list, status, and instructions apply, inferring or prompting for a change name to parse tasks and requirements.