openspec-verify-change

Verify change implementations against openspec artifacts for completeness and correctness.

Updated Mar 8, 2026

Search Tags:#code review #software quality #spec compliance #artifact analysis #change verification

Ready to run

npx skills add https://github.com/TranVanTienDat/barber-shop --skill openspec-verify-change-tranvantiendat

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: openspec-verify-change
Source: https://github.com/TranVanTienDat/barber-shop/tree/main/.agent/skills/openspec-verify-change
Command: npx skills add https://github.com/TranVanTienDat/barber-shop --skill openspec-verify-change-tranvantiendat

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill verifies that the implementation of a change matches the corresponding artifacts, ensuring accuracy and completeness before archiving.

Core Features & Use Cases

Change Verification: Validate that the implementation is complete, correct, and coherent.
Change Selection: Allows selection of a specific change or infers from context.
Task and Spec Coverage: Checks for task completion and spec coverage.
Implementation Mapping: Maps requirements to implementation evidence.
Design Adherence: Ensures implementation follows design decisions.
Code Pattern Consistency: Reviews new code for consistency with project patterns.

Quick Start

Use the openspec-verify-change skill to verify the implementation of the 'FeatureX' 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 changes match design artifacts before archiving?▼

Verifying code changes against artifacts involves mapping implementation evidence to requirements and design decisions. This process ensures completeness, correctness, and coherence by checking task completion and spec coverage before archiving.

What is change verification in software development workflows?▼

Change verification validates that an implementation matches corresponding change artifacts. It ensures completeness, correctness, and coherence by reviewing task completion, spec coverage, and code pattern consistency within software development workflows.

Do I need openspec to check implementation alignment with change artifacts?▼

Yes, you need the openspec CLI for artifact retrieval and analysis. It provides the necessary change artifacts to validate that your implementation follows design decisions and maintains code pattern consistency.

How do I check spec coverage and task completion for a specific change?▼

To check spec coverage and task completion, select a specific change or infer it from context. The verification process maps requirements to implementation evidence, ensuring all tasks and specifications are fully covered.

Can I review new code for consistency with project patterns during change verification?▼

Yes, during change verification you can review new code for consistency with project patterns. This ensures the implementation follows established design decisions and maintains coherence with existing software quality standards.

What are the limitations of automated artifact alignment for code review?▼

Automated artifact alignment relies on the openspec CLI for retrieval and analysis, meaning it requires properly structured change artifacts. It verifies coherence and design adherence but depends on accurate context inference for specific changes.