openspec-verify-change

Verify implementation matches OpenSpec change artifacts before archiving.

5|Updated Mar 21, 2026
One-click install
npx skills add https://github.com/8007342/tillandsias --skill openspec-verify-change-8007342
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-verify-change
Source: https://github.com/8007342/tillandsias/tree/main/.opencode/skills/openspec-verify-change
Command: npx skills add https://github.com/8007342/tillandsias --skill openspec-verify-change-8007342

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Before archiving a change in an OpenSpec workflow, teams need confidence that the implementation actually matches the planned specs, tasks, and design. 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 scorecard grouping findings into CRITICAL, WARNING, and SUGGESTION issues, 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 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 change name, or let it infer the change from context. It reads the change artifacts via the openspec CLI, checks tasks, specs, and design against the codebase, and outputs a report telling you whether the change is ready to archive.

What does the OpenSpec verification report check?▼

The report checks three dimensions: Completeness (task checkboxes and requirement coverage), Correctness (requirement implementation and scenario coverage in code), and Coherence (design adherence and code pattern consistency). Issues are grouped as CRITICAL, WARNING, or SUGGESTION.

Does openspec-verify-change work without a design document?▼

Yes, it degrades gracefully. If only tasks.md exists it verifies task completion only; with tasks and specs it checks completeness and correctness; with full artifacts it verifies all three dimensions, noting which checks were skipped.

What tools are required to run OpenSpec change verification?▼

The openspec CLI must be installed, since the workflow runs commands like openspec status, instructions, and list to load change artifacts. It also supports multi-store setups via the --store flag discovered with openspec store list.

What happens if verification finds incomplete tasks?▼

Each incomplete task checkbox becomes a CRITICAL issue with a recommendation to complete or mark it done. If any CRITICAL issues exist, the final assessment states the change must be fixed before archiving.