skills.rest
alexei-lexx
alexei-lexxCOMMUNITY
Explore all skills by this author →
GitHub

openspec-verify-change

Validate alignment between openspec change artifacts and implemented code.

Updated Jun 4, 2025
Search Tags:#quality-assurance#verify#openspec#code-review#specs#change-artifacts
One-click install
npx skills add https://github.com/alexei-lexx/budget --skill openspec-verify-change-alexei-lexx
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-verify-change
Source: https://github.com/alexei-lexx/budget/tree/main/.gemini/skills/openspec-verify-change
Command: npx skills add https://github.com/alexei-lexx/budget --skill openspec-verify-change-alexei-lexx

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Verify that an implementation accurately reflects the defined change artifacts (specs, tasks, and design) to prevent archiving incomplete or divergent work.

Core Features & Use Cases

  • Validate alignment between delta specs and the implemented code.
  • Generate a structured verification report covering Completeness, Correctness, and Coherence.
  • Identify missing or divergent elements and provide actionable recommendations.

Quick Start

Provide an optional change name; if omitted, the tool lists available changes and prompts you to select.

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

A verification report checks completeness, correctness, and coherence between delta specs and implemented code. It identifies missing or divergent elements and provides actionable recommendations to prevent archiving incomplete or divergent work.

How do I validate alignment between delta specs and implemented code?▼

You validate alignment by comparing change artifacts against implemented code to identify missing or divergent elements. The process generates a verification report providing actionable recommendations to ensure completeness, correctness, and coherence.

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

Yes, validating change artifacts requires the openspec CLI and access to delta artifacts stored in your project repository. Without these, the verification process cannot generate the structured completeness, correctness, and coherence report.

What is the best way to prevent archiving incomplete software changes?▼

The best way to prevent archiving incomplete software changes is to validate implementation against defined change artifacts to ensure completeness, correctness, and coherence. This generates a verification report identifying missing or divergent elements before archiving.

What does a verification report for change artifacts cover?▼

A verification report for change artifacts covers completeness, correctness, and coherence across delta specs and code. It identifies missing or divergent elements between defined artifacts and implemented code, providing actionable recommendations for resolution.

Related Skills

Explore More Software Engineering Skills→
DraculaboDraculabo
2.0k

openspec-verify-change

Verify OpenSpec delta implementations against specs, tasks, and design artifacts.

Community
Advanced
maxculen86maxculen86

sdd-archive

Merge delta specs into main specs and archive completed changes with dated reports.

Community
Advanced
BrennonTWilliamsBrennonTWilliams
7

ll-check-code

Execute linting, formatting, and type checking on project code.

Community
Basic
arestivoarestivo

openspec-verify-change

Verify software changes against specs, tasks, and design artifacts using the openspec CLI.

Community
Advanced