openspec-verify-change

Name: openspec-verify-change
Availability: InStock
Author: Zafar

Validate implementation against OpenSpec delta specs, tasks, and design artifacts.

Updated Apr 11, 2026

Search Tags:#artifacts #tasks #quality-assurance #verify #openspec #specs #change

Ready to run

npx skills add https://github.com/rafazafar/codex-octopus --skill openspec-verify-change-rafazafar

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: openspec-verify-change
Source: https://github.com/rafazafar/codex-octopus/tree/main/.agents/skills/openspec-verify-change
Command: npx skills add https://github.com/rafazafar/codex-octopus --skill openspec-verify-change-rafazafar

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

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

Core Features & Use Cases

Validate consistency between change artifacts and implementation.
Generate structured verification reports with CRITICAL, WARNING, and SUGGESTION issues.
Gracefully degrade: this skill can verify tasks-only or full artifact sets and clearly note skipped checks.

Quick Start

Run the OpenSpec verification workflow for a selected change.

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 software implementation matches change specs and design artifacts?▼

Verify implementation against change artifacts by parsing delta specs, tasks, and design documents to generate a structured report. This ensures your software change matches its intended design before archiving.

What is the best way to validate OpenSpec change implementations before archiving?▼

Validate OpenSpec change implementations by parsing artifacts, loading context, and assembling a structured verification report. This checks completeness, correctness, and coherence before you archive the change.

Can I verify tasks-only if my change is missing full design artifacts?▼

Yes, you can verify tasks-only. The validation gracefully degrades when full artifact sets are missing, clearly noting skipped checks while still processing available task definitions.

How does change verification categorize implementation issues?▼

Change verification categorizes issues into CRITICAL, WARNING, and SUGGESTION levels. This provides actionable recommendations to fix inconsistencies between your implementation and its delta specs.

What limitations should I expect when checking implementation consistency against change artifacts?▼

The main limitation is skipped checks when artifacts are incomplete. If your change lacks full specs, tasks, or design documents, the verification degrades gracefully but cannot validate missing artifact types.

Do I need complete delta specs to run quality assurance checks on a software change?▼

No, complete delta specs are not required. Quality assurance checks can verify tasks-only or full artifact sets, clearly noting any skipped checks when design or spec artifacts are absent.