openspec-verify-change

Verify software implementations against OpenSpec change specifications and artifacts.

1|Updated Apr 22, 2026
One-click install
npx skills add https://github.com/evandrodevbr/GeminiNexus --skill openspec-verify-change-evandrodevbr
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-verify-change
Source: https://github.com/evandrodevbr/GeminiNexus/tree/main/.claude/skills/openspec-verify-change
Command: npx skills add https://github.com/evandrodevbr/GeminiNexus --skill openspec-verify-change-evandrodevbr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps developers verify that implemented changes fully match their specifications, tasks, and design artifacts before they are archived.

Core Features & Use Cases

  • Implementation Verification: Checks completeness, correctness, and coherence between code changes and OpenSpec artifacts.
  • Artifact Analysis: Reviews tasks, requirements, scenarios, and design decisions to identify gaps or inconsistencies.
  • Use Case: Validate a completed feature branch by comparing its implementation against the related OpenSpec change documents and generating an actionable verification report.

Quick Start

Use the openspec-verify-change skill to verify that the current implementation matches the selected change 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 implementation matches change specifications before archiving?

Implementation verification compares your code changes against OpenSpec change documents, tasks, and requirements to identify gaps. It generates a verification report confirming completeness, correctness, and coherence before archiving the change.

What does an OpenSpec feature validation check for in a completed branch?

Feature validation reviews tasks, requirements, scenarios, and design decisions to identify gaps or inconsistencies. It checks coherence between your code changes and OpenSpec artifacts to ensure the implementation fully matches the specifications.

Do I need the openspec CLI to validate task completion and requirement coverage?

Yes, openspec CLI access is required to inspect change metadata, artifacts, and implementation evidence. The CLI provides the necessary interface to generate actionable verification reports for your completed features.

How do I check requirement coverage and design consistency for a software change?

Artifact analysis reviews your development artifacts and design decisions to ensure requirement coverage and design consistency. It identifies inconsistencies between the implemented code and the original OpenSpec change specifications.

When should I run an implementation validation report for my code review?

Run implementation validation before archiving a completed feature branch to verify that changes match OpenSpec artifacts. This ensures task completion checks pass and requirement coverage is confirmed prior to final code review.

Can I generate an actionable verification report comparing code to OpenSpec artifacts?

Yes, the skill validates completed feature branches by comparing implementations against related OpenSpec change documents. It generates an actionable verification report detailing any gaps or inconsistencies found during the review.