openspec-verify-change

Verify code implementations against change artifacts using the openspec CLI.

Updated Mar 8, 2026

Search Tags:#testing #code review #verification #compliance #change management #openspec

Ready to run

npx skills add https://github.com/deicer/codex-lb --skill openspec-verify-change-deicer

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: openspec-verify-change
Source: https://github.com/deicer/codex-lb/tree/main/.agents/skills/openspec-verify-change
Command: npx skills add https://github.com/deicer/codex-lb --skill openspec-verify-change-deicer

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires openspec, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill ensures that code implementations accurately reflect the intended design, specifications, and tasks, preventing drift and ensuring quality before archiving changes.

Core Features & Use Cases

Automated Verification: Checks for completeness, correctness, and coherence between code and change artifacts.
Issue Identification: Flags incomplete tasks, missing requirements, spec/design divergences, and code pattern inconsistencies.
Use Case: After a developer completes a new feature, they can use this Skill to automatically verify that all defined requirements are met, the design is adhered to, and the code is consistent with project standards before merging or archiving the work.

Quick Start

Use the openspec-verify-change skill to verify the implementation for the change named 'user-authentication-flow'.

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 code implementation matches design specs and tasks?▼

To verify code implementation matches design specs, you can run automated checks for completeness, correctness, and coherence against change artifacts. This process flags incomplete tasks, missing requirements, and spec divergences before merging or archiving.

What is change verification in software engineering?▼

Change verification in software engineering is the process of ensuring code implementations align with specified change artifacts, including specs, tasks, and design documents. It prevents drift and ensures quality by analyzing requirement coverage and design adherence.

How do I check for missing requirements and spec divergences before archiving code changes?▼

To check for missing requirements and spec divergences before archiving, execute change verification commands to list and apply change instructions. This programmatically generates a verification report identifying incomplete tasks and code pattern inconsistencies.

Do I need openspec to verify requirement coverage and task completion?▼

Yes, you need openspec installed to verify requirement coverage and task completion. The Skill operates by executing the openspec CLI to list, status, and apply change instructions, then programmatically generating a verification report assessing coherence.

What is the best way to prevent drift between code and design documents?▼

The best way to prevent drift between code and design documents is to perform automated verification that assesses completeness, correctness, and coherence. This ensures code implementations accurately reflect the intended design and specifications before archiving changes.

Why does my code implementation lack coherence with the defined change artifacts?▼

Your code implementation lacks coherence with defined change artifacts due to incomplete tasks, missing requirements, spec or design divergences, and code pattern inconsistencies. Running a verification check identifies these specific issues programmatically.