skills.rest
jacobcy
jacobcyCOMMUNITY
Explore all skills by this author →
GitHub

openspec-verify-change

Verify implementation against openspec change artifacts and output a prioritized issue report.

6|Updated Feb 5, 2026
Search Tags:#spec-driven#verification#reporting#tasks#openspec#code-review#change-management
One-click install
npx skills add https://github.com/jacobcy/vibe-coding-control-center --skill openspec-verify-change-jacobcy
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-verify-change
Source: https://github.com/jacobcy/vibe-coding-control-center/tree/main/.github/skills/openspec-verify-change
Command: npx skills add https://github.com/jacobcy/vibe-coding-control-center --skill openspec-verify-change-jacobcy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps ensure an implementation actually matches its change artifacts—tasks, delta specs, and design notes—so teams do not archive or close work that is incomplete, incorrect, or incoherent.

Core Features & Use Cases

  • Change selection and discovery: Prompts the user to choose a change when ambiguous and lists changes that have implementation tasks.
  • Artifact inspection: Uses openspec status and instructions to load contextFiles, tasks.md, delta specs, and design.md for the change.
  • Three-dimension verification: Produces a structured report covering Completeness (task checkboxes and spec requirements), Correctness (requirement-to-code mapping and scenario coverage), and Coherence (design adherence and pattern consistency).
  • Actionable reporting: Outputs a prioritized scorecard with CRITICAL, WARNING, and SUGGESTION items and concrete recommendations with file/line references where available.
  • Use cases: Pre-archive validation, release gating, QA/handoff readiness checks, and developer review assistance.

Quick Start

Ask the skill to verify the change named change-name to generate a verification report listing 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 change implementation against spec artifacts before archiving?▼

To verify change implementation before archiving, use spec-driven verification to inspect tasks.md, delta specs, and design.md against the actual code. It outputs a prioritized scorecard with CRITICAL, WARNING, and SUGGESTION issues and file references.

What is spec-driven verification for code changes?▼

Spec-driven verification is a process that validates whether a code implementation matches its change artifacts across three dimensions: Completeness, Correctness, and Coherence. It ensures teams do not archive work that is incomplete, incorrect, or incoherent.

How do I generate a verification report for missing tasks and unimplemented requirements?▼

Generate a verification report by instructing the tool to verify a specific change. It analyzes contextFiles, tasks.md, delta specs, and design.md to identify missing tasks, unimplemented requirements, and design inconsistencies, producing a structured scorecard.

Can I use openspec to check requirement-to-code mapping and scenario coverage?▼

Yes, openspec verification checks requirement-to-code mapping and scenario coverage as part of its Correctness dimension. It loads change context using openspec status and instructions to inspect delta specs and validate that all scenarios are implemented.

Do I need the openspec CLI to validate change context files?▼

Yes, the openspec CLI is required to validate change context files. The verification process depends on the CLI to load contextFiles, tasks.md, delta specs, and design.md for the selected change before producing its prioritized report.

When should I use change verification reporting in software engineering?▼

Use change verification reporting for pre-archive validation, release gating, QA and handoff readiness checks, or developer review assistance. It prevents closing work that is incomplete or incoherent by validating implementations against change artifacts.

Related Skills

Explore More Software Engineering Skills→
fkoschifkoschi
2

openspec-verify-change

Verify code implementations match specified Openspec change artifacts and generate a detailed report.

Community
Advanced
julian-panijulian-pani
2

code-review

Review git working tree changes for quality, security, and maintainability issues.

Community
Intermediate
hiro1989hiro1989
1

openspec-verify-change

Verifies code implementations match specified change artifacts using openspec CLI.

Community
Advanced
rock-hurock-hu

openspec-verify-change

Verify OpenSpec change implementations against specs, tasks, and design artifacts.

Community
Advanced