openspec-verify-change

Name: openspec-verify-change
Availability: InStock
Author: runecalico-ai

Verify code implementations against specs, tasks, and designs using the openspec CLI.

Updated Jan 9, 2026

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

Ready to run

npx skills add https://github.com/runecalico-ai/second_edition_spellbook --skill openspec-verify-change-runecalico-ai

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: openspec-verify-change
Source: https://github.com/runecalico-ai/second_edition_spellbook/tree/main/.cursor/skills/openspec-verify-change
Command: npx skills add https://github.com/runecalico-ai/second_edition_spellbook --skill openspec-verify-change-runecalico-ai

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 changes defined in specifications, tasks, and designs, preventing discrepancies before archiving.

Core Features & Use Cases

Automated Verification: Checks for completeness, correctness, and coherence between code and change artifacts.
Issue Identification: Flags incomplete tasks, unimplemented requirements, design deviations, and code pattern inconsistencies.
Use Case: Before merging a new feature, use this Skill to automatically verify that all associated tasks are done, the code correctly implements the specified requirements, and it adheres to the project's design principles.

Quick Start

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

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 change specifications and task artifacts?▼

You can verify code implementation against change artifacts by checking task completion for completeness, mapping requirements to code for correctness, and ensuring design adherence for coherence before archiving.

What does automated compliance checking for change management look for in code?▼

Automated compliance checking for change management flags incomplete tasks, unimplemented requirements, design deviations, and code pattern inconsistencies between the actual implementation and the specified change artifacts.

When do I need to run verification checks on change artifacts?▼

You need to run verification checks on change artifacts before merging a new feature to automatically verify that all associated tasks are done, requirements are correctly implemented, and design principles are strictly followed.

Do I need the openspec CLI to verify implementation completeness and spec coverage?▼

Yes, you need the openspec CLI installed for artifact management and status checks, as it is a required dependency to verify implementation completeness, correctness, and coherence against your change artifacts.

How do I check if code implementations adhere to project design principles?▼

Checking if code implementations adhere to project design principles involves verifying coherence by ensuring design adherence and maintaining code pattern consistency across all mapped requirements and scenarios.

What is the best way to prevent discrepancies between specifications and code before archiving?▼

The best way to prevent discrepancies between specifications and code before archiving is to perform automated verification that evaluates completeness, correctness, and coherence to catch unimplemented requirements and design deviations early.