openspec-verify-change

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

Verify a change's implementation against its delta specs, tasks, and design artifacts.

33|5|Updated Feb 24, 2026

Search Tags:#verification #audit #tasks #openspec #specs #change-artifacts #design-artifacts

Ready to run

npx skills add https://github.com/thelegendtubaguy/Qidi-Max-4-Optimized --skill openspec-verify-change-thelegendtubaguy

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: openspec-verify-change
Source: https://github.com/thelegendtubaguy/Qidi-Max-4-Optimized/tree/main/.pi/skills/openspec-verify-change
Command: npx skills add https://github.com/thelegendtubaguy/Qidi-Max-4-Optimized --skill openspec-verify-change-thelegendtubaguy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Verify that a change implementation aligns with its delta specs, tasks, and design artifacts before archiving to ensure traceability and quality.

Core Features & Use Cases

Delta verification: Compares the implemented change against the associated specs and tasks to detect gaps.
Artifact-aware checks: Integrates with OpenSpec to load context and verify planning, artifacts presence, and coverage.
Audit readiness: Produces a structured verification report highlighting completeness, correctness, and coherence for archival review.

Quick Start

Run the verification workflow to validate a specified change against its artifacts.

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 a software change matches its delta specs before archiving?▼

Verifying a software change before archiving involves comparing the implementation against its delta specs, tasks, and design artifacts. This process identifies gaps and ensures the change is complete, correct, and coherent for archival review.

What is artifact-aware verification for software changes?▼

Artifact-aware verification checks software changes by loading context files via the openspec CLI to validate planning, artifact presence, and coverage. It ensures implementation aligns with associated specs and tasks to detect gaps.

Do I need the openspec CLI to audit change artifacts?▼

Yes, you need the openspec CLI to audit change artifacts. The verification workflow requires the openspec CLI to analyze context files, load artifacts, and produce a structured report assessing completeness, correctness, and coherence.

How do I generate an audit report for software change completeness?▼

You generate an audit report by running a verification workflow that analyzes a specified change against its artifacts. It outputs a structured report highlighting completeness, correctness, and coherence assessments for archival review.

What is the best way to check delta specs and task coverage for a code change?▼

The best way to check delta specs and task coverage is to use an artifact-aware verification workflow that compares the implemented change against associated specs and tasks. This detects gaps and ensures alignment before archiving.