openspec-verify-change

Verify implementation matches OpenSpec change artifacts before archiving.

Updated Jul 31, 2026
One-click install
npx skills add https://github.com/germainlefebvre4/cvwonder-forms --skill openspec-verify-change-germainlefebvre4
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-verify-change
Source: https://github.com/germainlefebvre4/cvwonder-forms/tree/main/.gemini/skills/openspec-verify-change
Command: npx skills add https://github.com/germainlefebvre4/cvwonder-forms --skill openspec-verify-change-germainlefebvre4

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 Reporting: Generates a markdown report with a summary scorecard and issues grouped as CRITICAL, WARNING, or SUGGESTION, 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 a feature tracked as an OpenSpec change, run verification to confirm all tasks are checked off, every requirement has corresponding code, and the implementation follows the design decisions 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 by selecting a change name, then it checks task completion, spec coverage, and design adherence. It outputs a report with a summary scorecard and prioritized issues 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 (implementation mapping and scenario coverage), and Coherence (design adherence and code pattern consistency). Issues are grouped as CRITICAL, WARNING, or SUGGESTION.

Does openspec verify work 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 verifies completeness and correctness; the design adherence check is skipped and noted when no design document exists.

What happens if the change name is ambiguous during verification?

The workflow runs openspec list --json to retrieve available changes and prompts you to select one. It marks changes with incomplete tasks as In Progress and shows the schema used for each change.

What are the limitations of automated spec verification?

Correctness checks rely on keyword search and reasonable inference rather than guaranteed proof, so false positives are possible. The heuristic prefers lower-severity classifications when uncertain, and results should be reviewed before final archive decisions.