openspec-verify-change

Verifies code changes against openspec artifacts and generates a structured report.

4|2|Updated Aug 27, 2025
One-click install
npx skills add https://github.com/finger-gun/sisu --skill openspec-verify-change-finger-gun
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-verify-change
Source: https://github.com/finger-gun/sisu/tree/main/.kilocode/skills/openspec-verify-change
Command: npx skills add https://github.com/finger-gun/sisu --skill openspec-verify-change-finger-gun

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Verifies that a code change implements the required change artifacts and specifications before archiving, reducing risk of incomplete or incoherent changes.

Core Features & Use Cases

  • Validates delta specs against the codebase to confirm task completion and requirement coverage.
  • Assesses design coherence and traceability from specs to implementation.
  • Generates a structured verification report with actionable recommendations to guide archiving decisions.

Quick Start

Run the verification for a change using openspec and review the generated report.

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

You can verify code changes against specifications by analyzing delta specs, tasks, and design decisions across the repository to determine completeness and correctness, generating a structured verification report with actionable recommendations before archiving.

What is delta spec verification and how does it work?

Delta spec validation works by parsing openspec outputs and reading context artifacts to assess task completion and requirement coverage, then reporting CRITICAL, WARNING, and SUGGESTION issues to guide your archiving decisions.

How do I check if a code change covers all implementation requirements?

Check requirement coverage by validating delta specs against the codebase to confirm task completion, assess design coherence and traceability from specs to implementation, and review the generated structured verification report for gaps.

Can I use openspec to validate change artifacts and design coherence?

Yes, openspec parses change artifacts and context outputs to validate design coherence and traceability from specs to implementation, determining completeness and correctness while generating a structured verification report with actionable archiving recommendations.

What is the best way to validate change management artifacts before archiving a repository change?

The best way to validate change management artifacts is to analyze delta specs, tasks, design decisions, and scenarios across the repository to determine completeness, correctness, and coherence, producing a report with CRITICAL, WARNING, and SUGGESTION issues.

Why does my code change verification report show CRITICAL issues?

A verification report shows CRITICAL issues when the code change does not match the required change artifacts and specifications, indicating incomplete task completion, missing requirement coverage, or incoherent design traceability that must be resolved before archiving.