openspec-verify-change

Verify implementation alignment with OpenSpec change artifacts and generate a report.

1|Updated Feb 22, 2026

Search Tags:#verification #code-quality #openspec #test-coverage #change-artifacts

Ready to run

npx skills add https://github.com/SiddharthChillale/cloud-operations-reasoning-agent --skill openspec-verify-change-siddharthchillale

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: openspec-verify-change
Source: https://github.com/SiddharthChillale/cloud-operations-reasoning-agent/tree/main/.opencode/skills/openspec-verify-change
Command: npx skills add https://github.com/SiddharthChillale/cloud-operations-reasoning-agent --skill openspec-verify-change-siddharthchillale

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

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

Core Features & Use Cases

Load delta artifacts from openspec for a given change
Validate task completion, spec coverage, and scenario presence
Map requirements to code evidence and assess design coherence

Quick Start

Run the verification against the target change to generate a structured 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 implementation against change artifacts before archiving?▼

To verify code implementation against change artifacts before archiving, load delta specs and related artifacts under openspec/changes to validate task completion, requirement coverage, and scenario handling. This generates a structured report confirming alignment.

What is openspec change verification and how does it work?▼

Openspec change verification confirms an implementation aligns with change artifacts by loading delta specs, validating task completion, mapping requirements to code evidence, and assessing design coherence to generate a verification report before archiving.

Do I need the openspec CLI to verify task completion and spec coverage?▼

Yes, openspec change verification requires the openspec CLI and access to artifact context. The CLI loads delta specs under openspec/changes to compare implementations and generate a structured verification report.

How do I check if requirements are covered by code evidence in openspec?▼

To check requirement coverage by code evidence in openspec, run the verification process against the target change. It maps requirements to code evidence and assesses design coherence to confirm completeness before archiving.

When should I run a verification report for spec changes?▼

You should run a verification report for spec changes before archiving to ensure completeness, correctness, and coherence. It validates that the implementation matches associated change artifacts like specs, tasks, and design documents.

What limitations exist when validating scenario handling with openspec?▼

Validation of scenario handling with openspec is limited to delta specs under openspec/changes and related artifacts. It requires the openspec CLI and artifact context access to successfully load, compare, and generate the verification report.