openspec-verify-change

Validate change artifacts for completeness and coherence before archiving.

Updated Apr 13, 2026
One-click install
npx skills add https://github.com/soyrochus/vulgata --skill openspec-verify-change-soyrochus
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-verify-change
Source: https://github.com/soyrochus/vulgata/tree/main/.claude/skills/openspec-verify-change
Command: npx skills add https://github.com/soyrochus/vulgata --skill openspec-verify-change-soyrochus

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Verify that a change's artifacts (specs, tasks, design) are complete and coherent before archiving.

Core Features & Use Cases

  • Validates alignment between delta specs and implementation artifacts.
  • Analyzes task completion, spec coverage, and design coherence to ensure quality before release.
  • Generates a structured verification report with actionable recommendations and references.

Quick Start

Provide the change name and context to the tool to initiate the verification workflow.

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 changes against specs before archiving?

To verify changes against specs before archiving, you provide the change name and context to initiate a workflow that validates artifact completeness, spec coverage, and design coherence, generating a structured verification report.

What does spec coverage validation check for in a code change?

Spec coverage validation checks that delta specs align with implementation artifacts, analyzing task completion and design adherence to ensure code changes are complete and coherent before release.

How do I check if my task completion and design artifacts are coherent?

You can check artifact coherence by running a verification workflow that analyzes task completion, spec coverage, and design adherence, producing a report with actionable recommendations and file references.

Can I use change verification for QA review of delta specs?

Yes, you can use change verification for QA review by providing the change name and context to validate delta specs, tasks, and design artifacts, yielding a structured report with correctness and completeness checks.

What is the best way to validate artifact completeness before archiving a change?

The best way to validate artifact completeness is to run a verification workflow that analyzes specs, tasks, and design artifacts, producing a structured report with actionable recommendations and file references.

When should I not use automated spec coverage validation?

You should not use automated spec coverage validation when a change lacks defined artifacts like specs, tasks, or design documents, as the workflow requires these inputs to analyze coherence and produce a verification report.