openspec-verify-change

Verify implementation completeness, correctness, and coherence against OpenSpec change artifacts.

Updated Mar 17, 2026
One-click install
npx skills add https://github.com/beliciobcardoso/mcp-postgres --skill openspec-verify-change-beliciobcardoso
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-verify-change
Source: https://github.com/beliciobcardoso/mcp-postgres/tree/main/.qwen/skills/openspec-verify-change
Command: npx skills add https://github.com/beliciobcardoso/mcp-postgres --skill openspec-verify-change-beliciobcardoso

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 decisions. This Skill automates that validation by cross-checking code against OpenSpec 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: Groups findings into CRITICAL, WARNING, and SUGGESTION levels, each with specific actionable recommendations and file references. - Graceful Degradation: Adapts verification depth based on available artifacts, from tasks-only checks to full spec and design validation. - 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 code follows the documented design before archiving. ## 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 a change name, or let it prompt you to select from available changes via openspec list. It checks task completion, requirement implementation, and design adherence, then outputs a report with issues grouped by severity.

What does the OpenSpec verification report check?▼

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

Does OpenSpec verification work without a design document?▼

Yes, it degrades gracefully based on available artifacts. With only tasks.md it verifies task completion; with tasks and specs it checks completeness and correctness; full artifacts enable all three dimensions. Skipped checks are noted in the output.

What do CRITICAL, WARNING, and SUGGESTION issues mean in verification?▼

CRITICAL issues like incomplete tasks or missing requirement implementations must be fixed before archiving. WARNING issues cover spec or design divergences that should be addressed. SUGGESTION issues flag minor pattern inconsistencies that are optional to fix.

What are the requirements to run OpenSpec change verification?▼

You need the openspec CLI installed and a project with OpenSpec change artifacts such as tasks.md, delta specs, or design.md. The workflow uses openspec list, status, and instructions commands to locate and load change context.