openspec-verify-change

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

Updated Aug 5, 2026
One-click install
npx skills add https://github.com/JhonMA82/api-starter --skill openspec-verify-change-jhonma82
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-verify-change
Source: https://github.com/JhonMA82/api-starter/tree/main/.opencode/skills/openspec-verify-change
Command: npx skills add https://github.com/JhonMA82/api-starter --skill openspec-verify-change-jhonma82

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Before archiving a change, teams need confidence that the implementation actually matches the planned specs, tasks, and design. This Skill automates that audit by cross-checking code against OpenSpec 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 scorecard grouping findings into CRITICAL, WARNING, and SUGGESTION issues, each with actionable recommendations and file/line 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 the verification 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 the openspec CLI: it reads the change's tasks, specs, and design artifacts, then checks task completion, requirement implementation, and design adherence. The output is a report with CRITICAL, WARNING, and SUGGESTION issues.

What does the OpenSpec verification report check?▼

The report checks three dimensions: Completeness (task checkboxes and spec coverage), Correctness (requirement implementation and scenario coverage), and Coherence (design adherence and code pattern consistency). Each issue includes a specific recommendation with file references.

Can I verify a change without a design.md file?▼

Yes, verification degrades gracefully based on available artifacts. With only tasks.md it checks task completion; with tasks and specs it also checks correctness; design adherence is skipped when no design document exists, and skipped checks are noted.

How do I verify a change in a specific OpenSpec store?▼

Run openspec store list --json to discover registered store ids, then append --store <id> to commands like status, instructions, list, and validate. The store flag stays sticky for the rest of the verification workflow.

What happens if the change name is ambiguous?▼

The workflow runs openspec list --json to retrieve available changes and prompts you to select one. Changes with incomplete tasks are marked as In Progress, and only changes with task artifacts are shown.