skills.rest
tim-hub
tim-hubCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

openspec-verify-change

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

2|Updated Mar 10, 2026
Search Tags:#design#qa#tasks#verify#openspec#specs#change
One-click install
npx skills add https://github.com/tim-hub/powerball --skill openspec-verify-change-tim-hub
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-verify-change
Source: https://github.com/tim-hub/powerball/tree/main/openspec-rewrite/skills/openspec-verify-change
Command: npx skills add https://github.com/tim-hub/powerball --skill openspec-verify-change-tim-hub

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams confirm that an OpenSpec change's implemented work aligns with the associated specifications, tasks, and design decisions, preventing drift before archiving.

Core Features & Use Cases

  • Verify alignment between delta specs and actual implementation across code, tests, and artifacts.
  • Inspect task lists for completeness and evidence of completed work.
  • Assess coherence with design decisions and identify potential gaps before release or archiving.

Quick Start

Provide the change name when prompted to start the verification process for OpenSpec 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 OpenSpec changes against specs and tasks?▼

Verifying OpenSpec changes involves parsing task lists, delta specs, and design artifacts to confirm an implementation's completeness, correctness, and coherence before the change is archived.

What does it mean to reconcile OpenSpec delta specs with an implementation?▼

Reconciling OpenSpec delta specs means inspecting whether the actual code, tests, and artifacts correctly reflect the planned specification changes and design decisions, preventing drift before release.

Do I need the OpenSpec CLI to validate change implementation readiness?▼

Yes, validating archival readiness for an OpenSpec change requires the OpenSpec CLI, along with your delta specs and context artifacts, to properly parse and verify the implementation.

How can I check if my task lists are complete before archiving an OpenSpec change?▼

You can check task list completeness by running a verification process that inspects the tasks associated with your OpenSpec change, looking for evidence of completed work and identifying potential gaps.

When should I use OpenSpec verification for design and spec alignment?▼

You should use OpenSpec verification when you need to assess coherence with design decisions, confirm that implemented work matches specifications, and identify gaps before releasing or archiving a change.

Related Skills

Explore More Software Engineering Skills→
PBH-BTNPBH-BTN
6.2k

openspec-verify-change

Automate verification of implementations against OpenSpec change artifacts.

Official
Advanced
rayxulnrayxuln
241

openspec-archive-change

Archive a completed OpenSpec change with validated artifacts and metadata.

Community
Advanced
nextbysamnextbysam

spec-archiving

Archive completed change proposals and merge specification deltas into living documentation.

Community
Advanced
memorysavermemorysaver

openspec-verify-change

Verify implementation completeness against openspec delta spec artifacts.

Community
Advanced