openspec-verify-change

Identify gaps between implemented changes and openspec artifacts with remediation references.

39|6|Updated Apr 22, 2025

Search Tags:#code-quality #openspec #delta-specs #change-verification #spec-coverage #task-parsing #design-adherence

Ready to run

npx skills add https://github.com/danielsogl/copilot-workflow-demo --skill openspec-verify-change-danielsogl

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: openspec-verify-change
Source: https://github.com/danielsogl/copilot-workflow-demo/tree/main/.github/skills/openspec-verify-change
Command: npx skills add https://github.com/danielsogl/copilot-workflow-demo --skill openspec-verify-change-danielsogl

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Verify that an implementation matches the change artifacts (specs, tasks, and design) to ensure completeness and coherence before archiving.

Core Features & Use Cases

Validates task completion against openspec context by parsing tasks.md and checkbox states.
Assesses delta specs for requirements and scenarios, and checks for their presence in code and tests.
Evaluates design adherence and code pattern coherence, providing targeted remediation and references.

Quick Start

Run openspec verification for a specific change with openspec-verify-change, provide the change name, and review the generated report.

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

To verify code changes against design specs, parse delta specs and tasks to identify gaps in requirement coverage, scenario validation, and design adherence. This generates a structured report highlighting critical gaps with concrete remediation steps and file path references.

What is change verification in an openspec workflow?▼

Change verification in an openspec workflow is the process of validating that an implementation matches change artifacts, ensuring completeness and coherence. It assesses task completion by parsing tasks.md and checkbox states against the loaded delta specs.

How do I check task completion status from tasks.md and checkbox states?▼

You can check task completion by parsing tasks.md files and evaluating checkbox states against the openspec context. This validates whether implemented changes fully cover the defined tasks and requirements before archiving.

Can I detect design adherence and code pattern inconsistencies automatically?▼

Yes, you can detect design adherence and code pattern inconsistencies by evaluating delta specs against the implementation. The verification process flags pattern inconsistencies and provides targeted remediation with specific file paths and line references.

Does openspec-verify-change require external dependencies to run?▼

No, openspec-verify-change does not require external dependencies to run. It operates directly on delta changes loaded via the openspec workflow, requiring only the change name to generate the verification report.

What is the best way to report gaps between implemented code and specifications?▼

The best way to report gaps between implemented code and specifications is to produce a structured verification report. This report highlights critical gaps, suggests concrete remediation with file paths and line references, and flags any design or pattern inconsistencies.