openspec-verify-change

Verify software implementations against change artifacts using the openspec CLI.

1|Updated Jan 11, 2026
One-click install
npx skills add https://github.com/CloudDevCrusader/riddle-rush-mono-repo --skill openspec-verify-change-clouddevcrusader
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-verify-change
Source: https://github.com/CloudDevCrusader/riddle-rush-mono-repo/tree/main/.claude/skills/openspec-verify-change
Command: npx skills add https://github.com/CloudDevCrusader/riddle-rush-mono-repo --skill openspec-verify-change-clouddevcrusader

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill ensures that code implementations accurately reflect the intended design and requirements outlined in change artifacts, preventing discrepancies before archiving.

Core Features & Use Cases

  • Completeness Check: Verifies that all defined tasks and requirements are addressed.
  • Correctness Validation: Assesses if the implementation aligns with specified requirements and scenarios.
  • Coherence Assessment: Checks adherence to design decisions and project coding patterns.
  • Use Case: After a developer implements a new feature based on a specification document, this Skill can be used to automatically verify that all aspects of the specification have been correctly implemented and that the code follows established design principles.

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 against specifications before archiving changes?

To verify code implementation against specifications, this Skill checks that software implementations accurately match associated change artifacts, ensuring completeness, correctness, and coherence before archiving.

How does requirement coverage validation work for change management tasks?

Requirement coverage validation works by mapping implementations to defined requirements and scenarios, assessing task completion and design adherence to ensure code pattern consistency across change artifacts.

Do I need the openspec CLI to check if my implementation matches design documents?

Yes, you need the openspec CLI installed to check implementation matching, as the Skill requires it to list, status, and apply change instructions during the verification process.

What is the best way to assess code coherence and adherence to design decisions?

The best way to assess code coherence is using this Skill to evaluate design adherence and code pattern consistency, ensuring your implementation accurately reflects the intended design outlined in change artifacts.

Can I automatically validate that all specification tasks are addressed in my code?

You can automatically validate that all specification tasks are addressed by running a completeness check that verifies all defined tasks and requirements are covered in the implementation.

Why does implementation verification fail when mapping code to requirements?

Implementation verification fails when mapping code to requirements if the completeness check detects unaddressed tasks, missing requirement coverage, or inconsistencies between the code patterns and specified design decisions.