openspec-verify-change

Name: openspec-verify-change
Availability: InStock
Author: max-loo

Validate code implementation against OpenSpec change artifacts and generate a verification report.

2|Updated Oct 13, 2025

Search Tags:#automation #testing #verification #openspec #code-review #change-artifacts #spec-coverage

Ready to run

npx skills add https://github.com/Max-Loo/multi-chat --skill openspec-verify-change-max-loo

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: openspec-verify-change
Source: https://github.com/Max-Loo/multi-chat/tree/main/.trae/skills/openspec-verify-change
Command: npx skills add https://github.com/Max-Loo/multi-chat --skill openspec-verify-change-max-loo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams confirm that a proposed change fully implements the intended artifacts by comparing against specs and tasks, ensuring coherence before archiving.

Core Features & Use Cases

Delta spec verification against code, tasks, and design context.
Automated status checks via the openspec CLI to determine completeness and traceability.
Structured verification reporting to guide archiving decisions and reduce risk.

Quick Start

Provide a change name to verify, then run the verification to generate a comprehensive 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, validate that the implementation matches change artifacts by searching delta specs under openspec/changes/<name>/specs and assessing task completion. This generates a structured verification report highlighting completeness, correctness, and coherence.

What is OpenSpec delta spec verification and how does it work?▼

OpenSpec delta spec verification compares an implementation against specs, tasks, and design context using the OpenSpec CLI. It searches for delta specs, loads available context artifacts, and assesses traceability to determine if a proposed change fully implements the intended artifacts.

How do I check spec coverage and task completion for a codebase change?▼

Checking spec coverage and task completion involves loading change artifacts and assessing the codebase against them. The verification process outputs a report with actionable recommendations and file references, ensuring coherence before archiving a change.

Can I automate change artifact validation using the OpenSpec CLI?▼

Yes, you can automate change artifact validation using the OpenSpec CLI by providing a change name to verify. The automated status checks determine completeness and traceability across specs, tasks, and design context, guiding archiving decisions and reducing risk.

Does OpenSpec verification work without external dependencies?▼

Yes, OpenSpec verification works without external dependencies. It independently searches for delta specs, loads context artifacts, and assesses task completion and spec coverage across the codebase to output a structured verification report.

Why does my code change fail coherence checks against design specs?▼

Code changes fail coherence checks when the implementation lacks traceability or does not fully match the intended design specs. The verification report highlights these completeness and correctness gaps, providing actionable recommendations and file references to resolve them.