openspec-verify-change

Verify implementation matches openspec change artifacts and produce a prioritized verification report.

Updated Mar 8, 2026
One-click install
npx skills add https://github.com/whatevertogo/Astrcode --skill openspec-verify-change-whatevertogo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-verify-change
Source: https://github.com/whatevertogo/Astrcode/tree/main/.codex/skills/openspec-verify-change
Command: npx skills add https://github.com/whatevertogo/Astrcode --skill openspec-verify-change-whatevertogo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Helps engineers and reviewers confirm that an implementation fully covers the change artifacts (tasks, delta specs, design) before archiving, reducing missed requirements, regressions, and ambiguous handoffs.

Core Features & Use Cases

  • Change selection and discovery: Guides the user to select an explicit change via openspec list and prevents automatic or ambiguous selection.
  • Artifact inspection: Parses openspec status and instructions to load tasks.md, delta specs, design.md, and other context files for analysis.
  • Three-dimension verification: Produces a structured report covering Completeness (tasks and requirements), Correctness (requirement mapping and scenario coverage), and Coherence (design adherence and pattern consistency).
  • Actionable, prioritized output: Emits CRITICAL, WARNING, and SUGGESTION items with concrete recommendations and file/line references where available to drive fixes before archive.

Quick Start

Select the target change, run the openspec status and instructions apply flows to load artifacts, and generate a verification report that lists critical, warning, and suggestion items with concrete recommendations.

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 implementation matches change artifacts before archiving?

To verify implementation matches change artifacts, select an explicit change via openspec list, load tasks.md and delta specs, then generate a prioritized verification report covering completeness, correctness, and coherence with actionable recommendations.

How does spec validation work for change management?

Verification requires the openspec CLI, access to change context files like tasks.md and design.md, and codebase search capabilities to parse status, load artifacts, and produce a prioritized verification report with actionable file and line references.

Do I need the openspec CLI to validate task completion and requirements?

Verification requires the openspec CLI, access to change context files like tasks.md and design.md, and codebase search capabilities to parse status, load artifacts, and produce a prioritized verification report with actionable file and line references.

What's the best way to check code review coverage for delta specs and design documents?

The best way to check delta spec coverage is applying three-dimension verification to analyze completeness, correctness, and coherence, ensuring requirement mapping and scenario coverage match design patterns before archiving changes.

Why does openspec status prevent automatic change selection during verification?

Preventing automatic change selection ensures verification targets an explicit, unambiguous change, avoiding missed requirements and regressions by forcing the user to select the correct change context files for analysis.