openspec-verify-change

Verify implementation matches change artifacts using the openspec CLI.

Updated Jan 26, 2026
One-click install
npx skills add https://github.com/brandon-setegn/kafka-test --skill openspec-verify-change-brandon-setegn
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-verify-change
Source: https://github.com/brandon-setegn/kafka-test/tree/main/.cursor/skills/openspec-verify-change
Command: npx skills add https://github.com/brandon-setegn/kafka-test --skill openspec-verify-change-brandon-setegn

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps confirm that an implementation actually matches its change artifacts before a change is archived, reducing the risk of shipping incomplete or inconsistent work.

Core Features & Use Cases

  • Task Completion Review: Checks task checkboxes to identify unfinished work that still needs implementation.
  • Spec Coverage Analysis: Compares delta requirements and scenarios against the codebase to find missing or weakly covered behavior.
  • Design and Coherence Check: Reviews design decisions and code patterns to spot divergence, inconsistencies, or likely regressions.
  • Use Case: A team finishes a spec-driven feature and wants a fast verification pass that highlights what is done, what is missing, and what should be reviewed before archiving.

Quick Start

Ask the skill to verify a named change against its tasks, specs, and design artifacts.

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 that my code matches spec requirements before archiving a change?

Spec validation before archiving compares delta requirements and scenarios against the codebase to identify missing or weakly covered behavior. It checks task completion, spec coverage, and design coherence to highlight unfinished work and prevent shipping incomplete implementations.

What is spec-driven development change verification?

Spec-driven change verification confirms an implementation matches its change artifacts by mapping evidence against documented expectations. It reviews task checkboxes, requirements, scenarios, and design decisions to spot divergences, inconsistencies, or likely regressions before archiving.

Do I need the openspec CLI to run a code audit on change artifacts?

Yes, spec validation requires the openspec CLI to read change context files and map evidence against documented expectations. The CLI provides the necessary framework to parse task lists, requirements, and design decisions for implementation verification.

How do I check task completion and design coherence in a pre-archive review?

Pre-archive review checks task checkboxes to identify unfinished work, then compares delta requirements and scenarios against the codebase. It also reviews design decisions and code patterns to spot divergence, inconsistencies, or likely regressions before the change is archived.

What is the best way to find missing requirements in a spec-driven implementation?

Spec coverage analysis compares documented delta requirements and scenarios against the codebase to find missing or weakly covered behavior. This fast verification pass highlights what is done, what is missing, and what should be reviewed before archiving.

When should I not use automated spec validation for change management?

Spec validation is not suitable for changes lacking documented artifacts, requirements, or design decisions. It relies on reading change context files to map evidence against documented expectations, so undocumented or ad-hoc code changes cannot be verified through this workflow.