openspec-verify-change

Verify software implementations against OpenSpec change artifacts with priority-scored reports.

6|1|Updated Dec 19, 2025
One-click install
npx skills add https://github.com/ilaziness/vexo --skill openspec-verify-change-ilaziness
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-verify-change
Source: https://github.com/ilaziness/vexo/tree/main/.crush/skills/openspec-verify-change
Command: npx skills add https://github.com/ilaziness/vexo --skill openspec-verify-change-ilaziness

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires openspec.

What problem does it solve?

This skill helps you confirm that a code implementation truly matches the change artifacts (tasks, specs, and optional design) before you archive or close out work.

Core Features & Use Cases

  • Change Selection & Discovery: Lets users choose a specific change from openspec list --json without guessing, including marking changes with incomplete tasks as (In Progress).
  • Artifact-Driven Verification: Applies the chosen change to load artifact context via openspec instructions apply, then checks tasks, requirements, scenarios, and design (when present).
  • Actionable Verification Report: Produces a structured report with Completeness, Correctness, and Coherence, categorizing issues as CRITICAL, WARNING, or SUGGESTION with specific recommendations.

Quick Start

Use the openspec-verify-change skill to verify that your implementation matches the selected change artifacts in your OpenSpec workflow.

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 code implementation matches my software requirements and change specs?

Spec verification validates that your software implementation matches change artifacts across tasks, requirements, scenarios, and design. It checks completeness, correctness, and coherence before you archive or close out work.

How do I check if all OpenSpec change tasks and requirements are fully implemented before release?

You can verify release readiness by loading change artifacts via the openspec CLI, parsing checklists for task completion, and mapping keyword-based evidence to requirements to produce a priority-scored verification report.

What is the best way to validate architecture coherence and requirements mapping for a spec-driven change?

Architecture coherence and requirements mapping are validated by checking the implementation against selected change artifacts. This produces a structured report categorizing issues as CRITICAL, WARNING, or SUGGESTION with specific recommendations.

Do I need the openspec CLI installed to verify change artifacts and spec compliance?

Yes, the openspec CLI is required as a dependency. The verification process uses it to discover changes via `openspec list --json` and load artifact context through `openspec instructions apply`.

Why does my spec verification report show a change as In Progress instead of complete?

A change is marked as In Progress when the spec verification process detects incomplete tasks within the selected change artifacts. This prevents prematurely archiving work that lacks full implementation coverage.

Can I use openspec-verify-change to check scenario coverage and design coherence for my changes?

Yes, openspec-verify-change checks scenarios and optional design artifacts when present. It applies the chosen change to load artifact context and validates implementation coherence across all available spec components.