openspec-verify-change

Name: openspec-verify-change
Availability: InStock
Author: tatargabor

Validate a change's implementation against delta specs and design artifacts.

30|6|Updated Jan 26, 2026

Search Tags:#testing #spec #verify #openspec #code-review #artifact #change

Ready to run

npx skills add https://github.com/tatargabor/wt-tools --skill openspec-verify-change-tatargabor

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: openspec-verify-change
Source: https://github.com/tatargabor/wt-tools/tree/main/.claude/skills/openspec-verify-change
Command: npx skills add https://github.com/tatargabor/wt-tools --skill openspec-verify-change-tatargabor

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams verify that a change's implementation aligns with the defined specs, tasks, and design artifacts before archiving, reducing risk of drift and rework.

Core Features & Use Cases

Artifact-based verification: checks that all delta specs and tasks are represented in the codebase.
Traceability mapping: links requirements in specs to implementation files and tests.
Quality reporting: produces a structured verification report highlighting completeness, correctness, and coherence.

Quick Start

Run the verifier for a specific change to generate a comprehensive verification 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 against specs before archiving?▼

To verify code changes against specs, this workflow scopes to delta specs generated by the openspec tool, analyzes artifacts, maps requirements to code and tests, and produces a structured verification report.

What is artifact-based spec verification?▼

Artifact-based spec verification checks that all delta specs and tasks are represented in the codebase, using traceability mapping to link requirements in specs directly to implementation files and tests across the repository.

How do I map requirements to tests and implementation files across my repository?▼

You can map requirements to tests and implementation files using traceability mapping, which links specifications to the actual codebase to ensure cross-reference validation and confirm that implementation aligns with design artifacts.

How do I generate a structured verification report for code review?▼

A structured verification report for code review is generated by running the verifier for a specific change, highlighting completeness, correctness, and coherence by validating delta specs against repository code and tests.

When do I need to validate delta specs in a software project?▼

You need to validate delta specs before archiving a change to reduce the risk of drift and rework, ensuring the implementation satisfies requirements for status checks, artifact loading, and cross-reference validation.