openspec-verify-change

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

Updated Jan 31, 2026
One-click install
npx skills add https://github.com/thewoolleyman/personal-knowledge-base --skill openspec-verify-change-thewoolleyman
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-verify-change
Source: https://github.com/thewoolleyman/personal-knowledge-base/tree/main/.claude/skills/openspec-verify-change
Command: npx skills add https://github.com/thewoolleyman/personal-knowledge-base --skill openspec-verify-change-thewoolleyman

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 specs, tasks, and design documents. This Skill automates that audit so incomplete tasks, unimplemented requirements, and design drift are caught before archive. ## 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 Report: 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 docs are missing. - 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 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 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 produces a report with CRITICAL, WARNING, and SUGGESTION issues.

What does the OpenSpec verification report check?▼

The report covers 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, actionable recommendation.

Does openspec-verify-change work without a design.md file?▼

Yes, it degrades gracefully. If only tasks.md exists it verifies task completion only; with tasks and specs it checks completeness and correctness; with full artifacts it verifies all three dimensions, noting which checks were skipped.

What are the requirements to run OpenSpec change verification?▼

You need the openspec CLI installed and a project with OpenSpec change artifacts under openspec/changes. The skill runs commands like openspec list, openspec status, and openspec instructions apply to gather artifacts.

When should I not rely on automated spec verification?▼

Automated verification uses keyword search and reasonable inference, so it can produce false positives on ambiguous requirements. Treat WARNING and SUGGESTION items as review prompts, and manually confirm subtle behavioral requirements or complex design decisions.