openspec-verify-change

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

Verify openspec changes for completeness, correctness, and coherence.

Updated Aug 27, 2026

Search Tags:#qa #verify #code-analysis #openspec #spec-validation #change-management #artifact-mapping

Ready to run

npx skills add https://github.com/bgzbgz/show-time --skill openspec-verify-change-bgzbgz

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Verifies that an openspec change is fully implemented, coherent, and aligned with its change artifacts, enabling safe archiving.

Core Features & Use Cases

Completeness verification: checks task completion and spec coverage.
Correctness verification: maps requirements to code implementations and evaluates adherence.
Coherence verification: ensures design decisions and patterns are followed, with guidance for any gaps.
Use Case: A developer runs the verifier after updating a delta change to ensure all tasks, specs, and design references align before archiving.

Quick Start

Run the openspec verifier on a 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 that code changes align with spec requirements?▼

Spec validation maps requirements to code implementations and evaluates adherence to ensure tasks, specs, and design references align. This verification checks task completion and spec coverage, generating a comprehensive report before archiving.

What is change artifact mapping in code analysis?▼

Change artifact mapping links change specifications to actual code implementations to evaluate coherence and completeness. It ensures design decisions and patterns are followed, verifying that requirements map correctly to their corresponding code changes.

When should I run a spec validation check on delta changes?▼

Run a spec validation check after updating a delta change to ensure all tasks, specs, and design references align before archiving. This verifies that the change is fully implemented, coherent, and safe for permanent storage.

Can I check task completion and spec coverage without manual review?▼

Yes, automated verification checks task completion and spec coverage by mapping requirements to code implementations and evaluating adherence. This generates a comprehensive verification report, eliminating the need for manual spec review.

Does the openspec verifier work for archiving completed changes?▼

Yes, the verifier enables safe archiving by confirming changes are fully implemented, coherent, and aligned with their change artifacts. It validates completeness, correctness, and coherence, ensuring the change is safe to archive.

What are the limitations of automated spec validation?▼

Automated spec validation identifies gaps in design decisions and provides guidance for misalignments, but requires complete change artifacts to function. It verifies coherence and adherence but cannot fix missing implementations or incomplete tasks.