openspec-verify-change

Verify implementation matches OpenSpec change artifacts before archiving.

1|Updated Jun 30, 2026
One-click install
npx skills add https://github.com/trutoman/Conjuros --skill openspec-verify-change-trutoman
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-verify-change
Source: https://github.com/trutoman/Conjuros/tree/main/.opencode/skills/openspec-verify-change
Command: npx skills add https://github.com/trutoman/Conjuros --skill openspec-verify-change-trutoman

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? It closes the gap between planned change artifacts (specs, tasks, design) and the actual code, catching incomplete tasks, unimplemented requirements, and design drift before a change is archived. ## Core Features & Use Cases - Three-Dimension Verification: Audits completeness (task checkboxes, spec coverage), correctness (requirement-to-code mapping, scenario coverage), and coherence (design adherence, pattern consistency). - Structured Report: Produces a markdown scorecard with CRITICAL, WARNING, and SUGGESTION issues, each paired with an actionable recommendation and file references. - Graceful Degradation: Adapts checks to available artifacts, verifying only tasks when specs or design files are missing. - Use Case: Before archiving a spec-driven change, run verification to confirm all tasks are checked off, every requirement has implementation evidence, and the code follows the documented design decisions. ## Quick Start Ask the assistant to verify that the implementation of a named OpenSpec change matches its specs, tasks, and design artifacts.

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 infer the change from context. It reads tasks, specs, and design artifacts via the openspec CLI, then reports incomplete tasks, unimplemented requirements, and design divergences.

What does the openspec verification report contain?

The report contains a summary scorecard across completeness, correctness, and coherence, plus grouped issues labeled CRITICAL, WARNING, or SUGGESTION. Each issue includes a specific recommendation with file and line references.

Does openspec verify-change require the openspec CLI?

Yes, the workflow depends on the openspec CLI for commands like status, instructions, list, and validate. Without the CLI installed, change artifacts cannot be discovered or read.

What happens if a change has no design document?

The verification degrades gracefully: with only tasks it checks task completion, with tasks and specs it also checks correctness, and design adherence is skipped with a note explaining which checks were omitted.

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

Run openspec store list --json to discover registered store ids, then pass --store <id> on commands that read or write specs and changes. Commands without a store flag act on the nearest local openspec directory.