openspec-verify-change

Validate implementation matches specs, tasks, and design before archiving.

Updated Apr 15, 2026
One-click install
npx skills add https://github.com/manishsinghmf/blink-with-anti --skill openspec-verify-change-manishsinghmf
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-verify-change
Source: https://github.com/manishsinghmf/blink-with-anti/tree/main/.cursor/skills/openspec-verify-change
Command: npx skills add https://github.com/manishsinghmf/blink-with-anti --skill openspec-verify-change-manishsinghmf

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Validate that an implementation matches the associated change artifacts (specs, tasks, and design) before archiving.

Core Features & Use Cases

  • Artifact consistency checks across specs, tasks, and design artifacts.
  • Completeness and correctness verification with actionable recommendations.
  • Pre-archive quality gate to reduce rework and risk.

Quick Start

Run the OpenSpec verification for a selected change to generate a comprehensive report prior to archiving.

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 match design and spec artifacts before archiving?

Spec compliance verification validates that your implementation matches associated change artifacts across specs, tasks, and design documents before archiving. It evaluates task completion, spec coverage, and design coherence to reduce rework risk.

What is OpenSpec change verification in software engineering workflows?

OpenSpec change verification is a pre-archive quality gate for software projects that checks artifact consistency across code, specs, and tasks. It generates a structured verification report assessing completeness, correctness, and design coherence for a selected change.

How do I run spec compliance checks for a selected change prior to archival?

Run the OpenSpec verification on a selected change to generate a comprehensive pre-archival report. The process evaluates artifact consistency, task completion, and spec coverage, providing actionable recommendations for any detected inconsistencies.

Can I validate design coherence and task completion without external dependencies?

Yes, change verification operates without external dependencies to evaluate design coherence and task completion. It directly assesses your software project's specs, tasks, and design artifacts to ensure implementation correctness before archiving.

Why does implementation archiving fail spec coverage validation?

Spec coverage validation fails when the implementation does not match the associated change artifacts. Running a pre-archive verification identifies these completeness and correctness gaps across code, specs, and design, emitting a report with actionable recommendations.

What is the best way to ensure artifact consistency across specs, tasks, and design?

The best way to ensure artifact consistency is to run a pre-archive quality gate that validates your implementation against associated change artifacts. This verifies completeness, correctness, and design coherence, reducing rework and risk before archival.