openspec-verify-change

Verify implementation completeness, correctness, and coherence against OpenSpec change artifacts.

3|1|Updated May 29, 2026
One-click install
npx skills add https://github.com/mambo-wang/CodingHub --skill openspec-verify-change-mambo-wang
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-verify-change
Source: https://github.com/mambo-wang/CodingHub/tree/main/.qoder/skills/openspec-verify-change
Command: npx skills add https://github.com/mambo-wang/CodingHub --skill openspec-verify-change-mambo-wang

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Before archiving a change in an OpenSpec-driven workflow, teams need confidence that the implementation actually matches the planned specs, tasks, and design decisions. This Skill automates that audit by cross-checking code against change artifacts and producing a structured verification report. ## Core Features & Use Cases - Three-Dimension Verification: Checks Completeness (task checkboxes, spec coverage), Correctness (requirement implementation, scenario coverage), and Coherence (design adherence, code pattern consistency). - Prioritized Issue Report: Generates a markdown report with a summary scorecard and issues grouped as CRITICAL, WARNING, and SUGGESTION, each with actionable recommendations and file references. - Graceful Degradation: Adapts verification depth based on available artifacts, verifying only tasks if specs or design documents are missing. - Use Case: After finishing implementation of a spec-driven change, run this Skill to confirm all tasks are checked off, every requirement has corresponding code, and the design decisions were followed before archiving the change. ## Quick Start Verify that my current OpenSpec change implementation is complete and ready to archive.

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 an OpenSpec change before archiving?▼

Run the verification workflow with a change name, or let it prompt you to select from available changes via openspec list. It reads the tasks, specs, and design artifacts, then checks implementation completeness, correctness, and coherence, producing a prioritized report.

What does the OpenSpec verification report contain?▼

The report includes a summary scorecard for Completeness, Correctness, and Coherence, plus issues grouped by severity: CRITICAL (incomplete tasks, missing requirements), WARNING (spec or design divergences), and SUGGESTION (pattern inconsistencies), each with actionable recommendations.

Does openspec-verify-change work without a design.md file?▼

Yes, it degrades gracefully. If only tasks.md exists it verifies task completion only; with tasks and specs it checks completeness and correctness; design adherence checks are skipped and noted when no design artifact exists.

What are the requirements to run OpenSpec change verification?▼

You need the openspec CLI installed and a project with OpenSpec change artifacts (tasks, specs, optionally design). The Skill runs commands like openspec list, status, and instructions apply to gather context before analyzing the codebase.

Can verification run on workspace-planning mode changes?▼

No. When openspec status reports actionContext mode as workspace-planning, the Skill explains that full workspace implementation verification is unsupported and stops, without inferring repo-local implementation ownership.