openspec-verify-change

Verify implementation matches OpenSpec change artifacts before archiving.

1|Updated Aug 13, 2026
One-click install
npx skills add https://github.com/Miftah-Fentaw/GymPulse --skill openspec-verify-change-miftah-fentaw
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-verify-change
Source: https://github.com/Miftah-Fentaw/GymPulse/tree/main/.qwen/skills/openspec-verify-change
Command: npx skills add https://github.com/Miftah-Fentaw/GymPulse --skill openspec-verify-change-miftah-fentaw

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 decisions. 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 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 checks based on available artifacts, verifying only tasks if 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 openspec CLI: select the change, load its artifacts via openspec status and openspec instructions apply, then check tasks, specs, and design against the codebase. The result is a report with issues grouped by severity.

What does the OpenSpec verification report check?▼

The report checks three dimensions: Completeness (task checkboxes and requirement coverage), Correctness (requirement implementation and scenario coverage), and Coherence (design adherence and code pattern consistency). Issues are classified as CRITICAL, WARNING, or SUGGESTION.

Does openspec-verify-change require the openspec CLI?▼

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

What happens if a change has no design document?▼

The verification degrades gracefully. If only tasks exist, it verifies task completion only; if tasks and specs exist, it checks completeness and correctness; design adherence is skipped and noted when no design.md is present.

Can I verify a change in a registered OpenSpec store?▼

Yes. Run openspec store list --json to discover 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.