openspec-verify-change

Verify implementation matches OpenSpec change artifacts before archiving.

Updated Sep 7, 2026
One-click install
npx skills add https://github.com/raphaelmans/spectralpointengineering --skill openspec-verify-change-raphaelmans
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-verify-change
Source: https://github.com/raphaelmans/spectralpointengineering/tree/main/.skillshare/skills/openspec-verify-change
Command: npx skills add https://github.com/raphaelmans/spectralpointengineering --skill openspec-verify-change-raphaelmans

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: Assesses 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 checks based on available artifacts, verifying only tasks when 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 (checkbox tasks and spec requirement coverage), Correctness (requirement-to-code mapping and scenario coverage), and Coherence (design decision adherence and code pattern consistency).

Does openspec verify-change require the openspec CLI?

Yes, the openspec CLI is required. The workflow runs commands like openspec status, openspec instructions apply, and openspec list to discover changes and load artifact file paths.

What happens if a change has no design document?

The verification degrades gracefully. With only tasks.md it checks task completion; with tasks and specs it checks completeness and correctness; design adherence checks are skipped and noted when design.md is absent.

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

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