openspec-verify-change

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

10|Updated Jul 7, 2026
One-click install
npx skills add https://github.com/joannanowakowska/plannning-poker-app --skill openspec-verify-change-joannanowakowska
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-verify-change
Source: https://github.com/joannanowakowska/plannning-poker-app/tree/main/.github/skills/openspec-verify-change
Command: npx skills add https://github.com/joannanowakowska/plannning-poker-app --skill openspec-verify-change-joannanowakowska

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill checks whether an implementation actually matches the planned change artifacts, helping you catch incomplete work, missing requirements, and design drift before archiving a change.

Core Features & Use Cases

  • Task completion review: Scans task checklists and flags anything still incomplete.
  • Requirement coverage validation: Compares delta specs against the codebase to find unimplemented or partially implemented requirements.
  • Scenario and design checks: Looks for missing scenario coverage and verifies implementation alignment with design decisions when available.
  • Use Case: Before archiving a change, use this Skill to confirm that the implementation, tasks, specs, and design all line up and to generate a structured verification report.

Quick Start

Use the openspec verify change skill to validate the named change against its tasks, specs, and design artifacts and return a complete verification 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 implementation matches change specs before archiving?

Spec review validates requirements coverage by comparing delta specs against the codebase to find unimplemented or partially implemented requirements, preventing incomplete work from being archived.

What is change validation for spec-driven development?

Change validation checks task completion, requirement coverage, and design alignment to ensure an implementation matches planned change artifacts before archiving.

How do I check task completion and requirement coverage in an OpenSpec repository?

You check task completion by scanning checklists for incomplete items and validate requirement coverage by comparing delta specs against the codebase to find unimplemented requirements.

Do I need the openspec CLI to validate change artifacts?

Yes, change validation requires the openspec CLI and access to change artifacts in a local OpenSpec repository or registered store to perform completeness and correctness reviews.

How do I detect design drift between implementation and design decisions?

You detect design drift by verifying implementation alignment with available design decisions and checking for missing scenario coverage during the change validation process.

What is the best way to review specs and scenarios before archiving a change?

The best way is running a structured verification process that checks task checklists, delta specs, and design context to generate a complete verification report before archiving.