openspec-verify-change

Verify implementation matches OpenSpec change artifacts before archiving.

Updated Aug 7, 2026
One-click install
npx skills add https://github.com/javakishore-veleti/lifting-diary-app --skill openspec-verify-change-javakishore-veleti
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-verify-change
Source: https://github.com/javakishore-veleti/lifting-diary-app/tree/main/.qwen/skills/openspec-verify-change
Command: npx skills add https://github.com/javakishore-veleti/lifting-diary-app --skill openspec-verify-change-javakishore-veleti

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 Ask the assistant to verify that the implementation of a specific OpenSpec change matches its specs, tasks, and design before archiving.

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, which checks task completion, requirement implementation, and design adherence. It produces a report with CRITICAL, WARNING, and SUGGESTION issues so you know whether the change is ready to archive.

What does the openspec verify workflow check?

It checks three dimensions: Completeness (task checkboxes and spec coverage), Correctness (requirement implementation and scenario coverage), and Coherence (design adherence and code pattern consistency). Each issue includes a specific recommendation.

Does openspec verification require the openspec CLI?

Yes, the workflow requires the openspec CLI to run commands like status, instructions, and list against the change artifacts. Without the CLI installed, the change artifacts cannot be read or validated.

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 checks completeness and correctness, and with full artifacts it checks all three dimensions. Skipped checks are noted in the report.

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 specs and changes. The store flag stays sticky for the rest of the verification workflow.