openspec-verify-change

Validate implemented changes against openspec artifacts and generate a verification report.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/anaclumos/verifidia --skill openspec-verify-change-anaclumos
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-verify-change
Source: https://github.com/anaclumos/verifidia/tree/main/.opencode/skills/openspec-verify-change
Command: npx skills add https://github.com/anaclumos/verifidia --skill openspec-verify-change-anaclumos

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams ensure that an implementation precisely satisfies the defined change artifacts (specs, tasks, and design) and is ready for archiving, reducing the risk of untracked or inconsistent changes.

Core Features & Use Cases

  • Load and parse openspec change artifacts (specs, tasks, design) to build a verification context.
  • Validate completeness by checking task checklists and delta-spec requirements.
  • Validate correctness by mapping requirements to code and assessing alignment with intent.
  • Validate coherence by comparing design decisions and coding patterns, and by generating a structured verification report.

Quick Start

Provide the change name (or allow inference) to run a full verification and generate the 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 change implementation against specs and tasks before archiving?

To verify change implementation before archiving, load openspec change artifacts, parse task checklists and delta-specs, map requirements to code, and generate a multi-dimensional verification report covering completeness, correctness, and coherence.

What is change verification in software projects using openspec artifacts?

Change verification in openspec projects identifies and validates that implemented changes align with specified artifacts like specs, tasks, and design, ensuring the implementation precisely satisfies defined requirements before archiving.

Can I validate multiple changes in a project using openspec verification?

Yes, openspec verification supports validating both a single change and multiple changes in a project by loading change artifacts and mapping requirements to code to assess alignment with intent.

What does a multi-dimensional verification report include for software changes?

A multi-dimensional verification report includes completeness validation by checking task checklists, correctness by mapping requirements to code, and coherence by comparing design decisions and coding patterns against specified artifacts.

How do I check completeness and correctness of delta-specs and task checklists?

To check completeness and correctness, parse task checklists and delta-spec requirements from openspec artifacts, map them to code, and assess alignment with the intended design decisions to validate the implementation.

Why does change archiving need design coherence validation?

Change archiving needs design coherence validation to reduce the risk of untracked or inconsistent changes by comparing coding patterns and design decisions against the specified openspec artifacts before finalizing.