openspec-verify-change

Verify implementation matches change specifications and test scenarios across codebases.

Updated Jan 9, 2026
One-click install
npx skills add https://github.com/Draft-Official/draft-web --skill openspec-verify-change-draft-official
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-verify-change
Source: https://github.com/Draft-Official/draft-web/tree/main/.claude/skills/openspec-verify-change
Command: npx skills add https://github.com/Draft-Official/draft-web --skill openspec-verify-change-draft-official

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps developers verify that their implementation accurately reflects change artifacts, ensuring correctness and completeness before archiving or deployment.

Core Features & Use Cases

  • Change Verification: Checks if implementation matches specified change artifacts like specs and tasks.
  • Status Assessment: Provides detailed reports on task completion, spec coverage, and scenario testing.
  • Use Case: When preparing a code update, use this Skill to ensure all requirements are implemented, tested, and aligned with design decisions, reducing errors and rework.

Quick Start

Use openspec-verify-change to validate the latest implementation against our change artifacts before releasing the update.

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 specifications before deployment?

To verify implementation matches change specifications, you systematically check code repositories against change artifacts and test scenarios to assess completeness, correctness, and coherence before archiving or deployment.

What is change verification in software quality assurance?

Change verification in software quality assurance is the process of validating that implementation accurately reflects specified change artifacts, specs, and tasks, ensuring correctness and completeness before archiving or deployment.

How do I check if my code update meets all task completion and spec coverage requirements?

To check task completion and spec coverage requirements, you assess code repositories against change artifacts to generate detailed reports on implementation completeness, scenario testing, and design alignment.

Do I need access to code repositories to run change specification verification?

Yes, change specification verification requires access to change artifacts, specifications, and code repositories to systematically assess implementation completeness, correctness, and coherence.

What's the best way to validate test scenarios across codebases for change management?

The best way to validate test scenarios across codebases for change management is to systematically compare implementation against change artifacts, ensuring all requirements are tested and aligned with design decisions to reduce rework.