openspec-verify-change

Verify OpenSpec change implementation against specs, tasks, and design artifacts.

Updated Jan 29, 2026

Search Tags:#design #verification #tasks #verify #specs #change-artifacts

Ready to run

npx skills add https://github.com/hongquandev/OpenSpec-VI --skill openspec-verify-change-hongquandev

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: openspec-verify-change
Source: https://github.com/hongquandev/OpenSpec-VI/tree/main/.agent/skills/openspec-verify-change
Command: npx skills add https://github.com/hongquandev/OpenSpec-VI --skill openspec-verify-change-hongquandev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Verify that a change's implementation matches its associated artifacts (specs, tasks, and design).

Core Features & Use Cases

Pull and compare artifacts (specs, tasks, design) for a change and verify implementation alignment.
Parse tasks to assess completion; check delta specs for coverage.
Generate a structured verification report with a severity-based issue list and actionable recommendations.

Quick Start

Provide the change name (or allow context inference), then run openspec status and openspec instructions apply to produce a verification 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 that my change implementation matches its specs and tasks?▼

To verify change implementation against artifacts, provide a change name or let the system infer it, then run openspec status and openspec instructions apply to generate a structured verification report.

What does a verification report for change artifacts include?▼

The verification report provides a severity-based issue list, assesses task completion, checks delta specs for coverage, and offers actionable recommendations to align implementation with design artifacts.

How to check if delta specs map correctly to code changes?▼

Checking delta spec coverage involves running openspec status to assess readiness and schema status, then parsing tasks and mapping delta specs to code to verify implementation alignment.

Can I verify scenario coverage and design conformance without specifying a change name?▼

Yes, the system can infer the change name from context, allowing you to verify scenario coverage and assess design conformance automatically before the change is stored.

What's the best way to validate OpenSpec changes before storing them?▼

Validating OpenSpec changes before storage requires checking artifact presence, readiness, and schema status, then producing a structured report with prioritized issues to ensure implementation matches specifications.

Why does my change verification report show incomplete task status?▼

Incomplete task status in the verification report indicates that parsed tasks within the change artifacts have not been fully implemented, requiring you to address the highlighted issues before storage.