openspec-verify-change

Verify implementation matches OpenSpec change artifacts before archiving.

1|1|Updated Jan 25, 2026
One-click install
npx skills add https://github.com/phuchoang2603/nixos --skill openspec-verify-change-phuchoang2603
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-verify-change
Source: https://github.com/phuchoang2603/nixos/tree/main/home/base/cli/skills/openspec-verify-change
Command: npx skills add https://github.com/phuchoang2603/nixos --skill openspec-verify-change-phuchoang2603

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/line references. - Graceful Degradation: Adapts checks based on available artifacts, verifying only tasks if specs or design documents are missing, and noting skipped checks. - 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 the current OpenSpec change 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, which selects the change, loads its tasks, specs, and design artifacts via the openspec CLI, then checks completeness, correctness, and coherence. It outputs a report 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 spec requirement coverage), Correctness (requirement implementation and scenario coverage in code), and Coherence (design decision adherence and code pattern consistency).

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; design adherence checks are skipped and noted when no design document exists.

What happens if the change name is ambiguous or missing?▼

The Skill infers the change from conversation context or auto-selects when only one active change exists. Otherwise it runs openspec list --json and prompts you to pick from available changes, marking incomplete ones as In Progress.

What are the limitations of automated spec verification?▼

Verification relies on keyword search and reasonable inference rather than perfect certainty, so false positives are possible. The heuristic prefers SUGGESTION over WARNING and WARNING over CRITICAL when uncertain to avoid overstating issues.