Verified:GitHub

openspec-verify-change

Verify implementation completeness against change artifacts and source code evidence.

Updated Jul 6, 2025

Search Tags:#verification #design consistency #spec review #implementation validation #requirement coverage #task auditing

Ready to run

npx skills add https://github.com/wishx127/mirror-server --skill openspec-verify-change-wishx127

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: openspec-verify-change
Source: https://github.com/wishx127/mirror-server/tree/main/.codebuddy/skills/openspec-verify-change
Command: npx skills add https://github.com/wishx127/mirror-server --skill openspec-verify-change-wishx127

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill checks whether an implementation truly matches the intended change so teams can catch missing work, incorrect behavior, and process drift before archiving.

Core Features & Use Cases

Task Completion Review: Confirms checklist items are finished and flags anything still open.
Requirement Coverage Analysis: Compares change requirements against code evidence to spot gaps.
Design and Coherence Validation: Reviews implementation against design decisions and project patterns to detect inconsistencies.
Use Case: A release manager uses this Skill to verify a completed feature branch against specs, tasks, and design notes before closing the change.

Quick Start

Use this skill to verify the selected change against its artifacts and summarize any completeness, correctness, or coherence 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 implementation against change specs and design notes?▼

Implementation verification involves comparing source code evidence against change specs, tasks, and design notes to confirm completeness, correctness, and coherence. This process catches missing work, incorrect behavior, and process drift before archiving a feature branch.

What is requirement coverage analysis and how does it spot gaps?▼

Requirement coverage analysis compares change requirements against actual code evidence to identify gaps. It checks whether every specified requirement has corresponding implementation proof, ensuring no intended functionality is missing from the final source code.

How do I audit task completion for a feature branch before closing?▼

Task completion auditing confirms checklist items are finished and flags anything still open. A release manager uses this to review a completed feature branch against its tasks, ensuring all required work is truly done before archiving.

What's the best way to validate design consistency across a codebase?▼

Design consistency validation reviews implementation against design decisions and project patterns to detect inconsistencies. This ensures the codebase adheres to established architectural choices and maintains coherence with the intended project design.

What do I need to perform spec-driven change review?▼

Spec-driven change review requires access to change specs, tasks, design notes, and source code evidence. These artifacts provide the baseline needed to confirm implementation completeness, correctness, and coherence before the change is archived.