openspec-verify-change

Verify implementation matches change artifacts and generate a structured verification report.

Updated Jan 30, 2026
One-click install
npx skills add https://github.com/guillaumejay/FileIndexer --skill openspec-verify-change-guillaumejay
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-verify-change
Source: https://github.com/guillaumejay/FileIndexer/tree/main/.gemini/skills/openspec-verify-change
Command: npx skills add https://github.com/guillaumejay/FileIndexer --skill openspec-verify-change-guillaumejay

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Verifies that an implementation matches change artifacts (specs, tasks, and design) to ensure accurate, complete archival.

Core Features & Use Cases

  • Completeness checks: verify tasks, delta specs, and artifacts exist and are aligned.
  • Correctness checks: map requirements to code and detect potential divergences.
  • Coherence checks: ensure design decisions are reflected in implementation and follow project patterns.

Quick Start

Provide the change name to verify, or let the tool prompt you to select from available changes.

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

Change verification checks completeness, correctness, and coherence by mapping requirements to code and detecting divergences. It ensures delta specs are fully implemented and aligned with design across features before archiving.

How do I check if a software implementation is complete against its task list?

You check implementation completeness by parsing tasks from change artifacts and verifying that each task has corresponding code artifacts, ensuring delta specs are fully implemented and aligned across features.

What is the best way to detect divergences between delta specs and code implementation?

Correctness checks map requirements to code to detect divergences between the implementation and change artifacts. This ensures the delta specs are accurately reflected in the actual software change.

Can I generate a structured verification report for software change artifacts?

Yes, the change verification process generates a structured verification report after loading artifacts, parsing tasks, mapping specs, and executing correctness checks to confirm the implementation matches the design.

Does change verification work without specifying a change name?

Yes, if you do not provide a change name, the tool prompts you to select from available changes so it can load the correct artifacts and execute the verification workflow automatically.