openspec-verify-change

Verify implementation matches OpenSpec change artifacts before archiving.

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

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 references. - Graceful Degradation: Adapts verification depth based on available artifacts, verifying only tasks when specs or design docs are missing. - Use Case: After finishing a feature tracked by an OpenSpec change, run verification to confirm all tasks are checked off, every requirement has implementation evidence, and the design decisions were followed before archiving the change. ## 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 the change name, or let it be inferred from context. The skill reads the change's tasks, specs, and design via the openspec CLI, then checks completeness, correctness, and coherence, producing a report of issues to fix before archiving.

What does the openspec verification report contain?

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

Does openspec-verify-change require the openspec CLI?

Yes, the skill requires the openspec CLI to be installed. It runs commands like openspec status, openspec instructions apply, and openspec list to discover changes and load artifact file paths for verification.

What happens if a change has no design document?

The skill degrades gracefully. With only tasks.md it verifies task completion; with tasks and specs it checks completeness and correctness; design adherence is only checked when a design.md exists, and skipped checks are noted in the report.

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

Run openspec store list --json to find registered store ids, then the skill appends --store <id> to commands that read or write specs and changes. The flag stays sticky for the rest of the verification workflow.