openspec-verify-change

Verify code implementations against change artifacts using the openspec CLI.

1|Updated Feb 11, 2026

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

Ready to run

npx skills add https://github.com/vidos-id/usecase-demos --skill openspec-verify-change-vidos-id

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: openspec-verify-change
Source: https://github.com/vidos-id/usecase-demos/tree/main/.agents/skills/openspec-verify-change
Command: npx skills add https://github.com/vidos-id/usecase-demos --skill openspec-verify-change-vidos-id

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

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

Core Features & Use Cases

Automated Verification: Checks for task completion, spec coverage, requirement implementation, and design adherence.
Issue Reporting: Generates a detailed report categorizing issues as CRITICAL, WARNING, or SUGGESTION with actionable recommendations.
Use Case: Before merging a new feature, use this Skill to automatically verify that all associated development tasks are done, all specified requirements are implemented in code, and the implementation aligns with the approved design.

Quick Start

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

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 change specifications before merging?▼

Automated verification checks code implementations against defined specifications, tasks, and design documents to ensure completeness and correctness. It generates a structured report categorizing issues as CRITICAL, WARNING, or SUGGESTION with actionable recommendations before merging.

What is change artifact verification in software engineering?▼

Change artifact verification assesses code implementations against predefined specs, tasks, and design documents to ensure completeness, correctness, and coherence. It prevents specification drift and ensures quality before archiving changes.

Do I need the openspec CLI to check code compliance with design documents?▼

Yes, checking implementation compliance requires the openspec CLI. The verification skill uses this CLI to list, status, and apply change instructions, enabling automated assessment of completeness, correctness, and design adherence.

How do I automate checking task completion and spec coverage for a new feature?▼

Automate task completion and spec coverage checks by running verification against the specific change artifact. The process evaluates requirement implementation and outputs a detailed report with actionable recommendations for critical and warning-level issues.

What's the best way to ensure code review compliance with predefined specifications?▼

The best way to ensure code review compliance is performing automated verification against change artifacts. This checks requirement implementation and design adherence, generating a categorized issue report to guide the review process before merging.

Why does my implementation verification report show critical issues before archiving?▼

A verification report shows critical issues when code implementations fail to accurately match defined specifications, tasks, or design documents. These critical findings indicate incomplete requirement implementation or design drift that must be resolved before archiving changes.