openspec-verify-change

Verify code implementations against tasks, specs, and design documents.

95|15|Updated Nov 25, 2025
One-click install
npx skills add https://github.com/jixoai/openspecui --skill openspec-verify-change-jixoai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-verify-change
Source: https://github.com/jixoai/openspecui/tree/main/.claude/skills/openspec-verify-change
Command: npx skills add https://github.com/jixoai/openspecui --skill openspec-verify-change-jixoai

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

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

Core Features & Use Cases

  • Automated Verification: Checks completeness, correctness, and coherence of implementation against specs and design.
  • Issue Reporting: Generates a detailed report highlighting critical, warning, and suggestion-level issues.
  • Use Case: Before merging a new feature, use this Skill to automatically verify that all defined requirements are met, tasks are completed, and the code adheres to the established design patterns.

Quick Start

Use the openspec-verify-change skill to verify the change named 'feature-x'.

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 design documents and requirements?

You can verify code implementation by parsing change artifacts like tasks.md, specs/, and design.md, cross-referencing them with the codebase to assess completeness, correctness, and coherence, and generating a structured report with actionable recommendations.

What is change artifact compliance and why is it needed before merging?

Change artifact compliance ensures that code implementations accurately reflect the intended design, requirements, and tasks, preventing inconsistencies before archiving. It is needed before merging to confirm all defined requirements are met.

How do I check if my codebase meets all tasks defined in tasks.md?

You can check if your codebase meets defined tasks by parsing tasks.md and specs/ within a change context, cross-referencing the codebase against these artifacts to evaluate task completion, and identifying any unmet requirements.

Does automated code review work with custom design.md and specs/ formats?

Automated verification supports custom design.md and specs/ formats by parsing these change artifacts directly, extracting requirements and design patterns to cross-reference with the codebase for adherence and coherence.

What is the best way to generate a report for unmet software requirements?

The best way to generate a report for unmet requirements is to cross-reference the codebase against change artifacts, automatically highlighting critical, warning, and suggestion-level issues with actionable recommendations for issues found.