skills.rest
jrmatherly
jrmatherlyCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

openspec-verify-change

Verify implementation against openspec change artifacts and generate prioritized reports.

Updated Apr 14, 2026
Search Tags:#spec-driven#verification#completeness#openspec#code-review#coherence#task-tracking
One-click install
npx skills add https://github.com/jrmatherly/spacebot --skill openspec-verify-change-jrmatherly
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-verify-change
Source: https://github.com/jrmatherly/spacebot/tree/main/.windsurf/skills/openspec-verify-change
Command: npx skills add https://github.com/jrmatherly/spacebot --skill openspec-verify-change-jrmatherly

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps reviewers and engineers verify that an implementation matches its change artifacts—specs, tasks, and design—so incomplete or divergent work is caught before a change is archived. It reduces manual audit time, prevents unfinished or inconsistent implementations from being considered complete, and produces actionable, prioritized findings.

Core Features & Use Cases

  • Guided change selection: Prompts the user to choose a change (using openspec list) and only proceeds with an explicit selection.
  • Artifact-driven verification: Loads contextFiles from openspec, inspects tasks.md, delta specs, design.md, and other artifacts to evaluate completeness, correctness, and coherence.
  • Prioritized, actionable report: Produces a three-dimension report (Completeness, Correctness, Coherence) with CRITICAL, WARNING, and SUGGESTION entries and specific file/line recommendations where available.
  • Use Case: A release engineer or code reviewer runs this to confirm a change is ready to archive by checking task completion, requirement implementation, scenario coverage, and adherence to design decisions.

Quick Start

Verify the implementation for change "my-change" by selecting it when prompted and generate a prioritized verification report indicating critical, warning, and suggestion issues.

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 completeness against change specs before archiving?▼

You can verify implementation completeness by loading contextFiles from openspec, inspecting tasks.md, delta specs, and design documents to evaluate task completion, requirement coverage, and scenario tests before archiving.

What is spec-driven verification for code review and how does it work?▼

Spec-driven verification validates that code implementations match change artifacts by parsing JSON exports, searching the codebase, and producing a prioritized report across three dimensions: Completeness, Correctness, and Coherence, with specific file and line recommendations.

How do I check if task tracking and requirement coverage match the design documents?▼

Check task tracking and requirement coverage by applying artifact-driven verification to inspect tasks.md and design documents, evaluating whether the implementation adheres to design decisions and scenario tests while ensuring all tracked tasks are completed.

Do I need the openspec CLI to perform spec-driven verification of change artifacts?▼

Yes, you need the openspec CLI to perform spec-driven verification, as it is required for listing changes, retrieving status, and exporting contextFiles that the verification process parses to evaluate implementation coherence and completeness.

Can I generate a prioritized report for code review issues found during change verification?▼

Yes, you can generate a prioritized report during change verification that categorizes issues into CRITICAL, WARNING, and SUGGESTION entries across Completeness, Correctness, and Coherence dimensions, providing specific file and line recommendations for actionable code review feedback.

What are the limitations of automated task completion verification before archiving a change?▼

Automated task completion verification requires explicit change selection and depends on openspec CLI contextFiles, meaning it cannot proceed without user selection and is limited to validating changes managed by the openspec workflow for requirement coverage and design coherence.

Related Skills

Explore More Software Engineering Skills→
futureteafuturetea

openspec-verify-change

Verify codebase implementations against openspec change artifacts and generate prioritized reports.

Community
Advanced
g1331g1331
3

openspec-verify-change

Verify an OpenSpec change implementation against its specs, tasks, and design.

Community
Advanced
VoDaiLoczVoDaiLocz
24

lint-and-validate

Automate linting and static analysis of code in CI pipelines.

Community
Intermediate
sachinnair90sachinnair90

openspec-verify-change

Verify implementation against change artifacts and generate a prioritized gap report.

Community
Advanced