openspec-verify-change

Validate change implementations against openspec delta specifications, tasks, and design context.

Updated May 29, 2025
One-click install
npx skills add https://github.com/crozzbite/DnDApp --skill openspec-verify-change-crozzbite
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-verify-change
Source: https://github.com/crozzbite/DnDApp/tree/main/.github/skills/openspec-verify-change
Command: npx skills add https://github.com/crozzbite/DnDApp --skill openspec-verify-change-crozzbite

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Verify that an implementation matches its change artifacts (specs, tasks, and design), ensuring completeness and coherence before archiving.

Core Features & Use Cases

  • Completeness verification: checks that tasks and delta specifications are fully addressed.
  • Correctness validation: maps each requirement to code paths and tests to ensure alignment with intent.
  • Coherence assessment: audits design decisions and coding patterns for consistency across the project.
  • Reporting: generates a structured verification report with actionable recommendations, highlighting CRITICAL, WARNING, and SUGGESTION issues.

Quick Start

Run the openspec-verify-change workflow to assess a selected change and generate a structured 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 code changes against delta specifications before archiving?

Spec validation for code changes checks that implementations align with delta specifications, tasks, and design context. It analyzes task completion and spec coverage across code, tests, and design docs to ensure correctness before archiving.

What does spec validation for code changes actually check?

Spec validation checks completeness, correctness, and coherence. It verifies that tasks and delta specifications are fully addressed, maps requirements to code paths and tests, and audits design decisions for consistency across the project.

Can I map specific requirements to code paths and tests during spec validation?

Yes, correctness validation maps each requirement to code paths and tests to ensure alignment with intent. This validates that delta specifications are accurately reflected in the actual implementation.

Do I need the openspec CLI to validate change implementations?

Yes, validating change implementations requires access to the openspec CLI and the change context artifacts. These are necessary to analyze task completion and produce a structured verification report.

How do I generate a structured verification report for unaddressed spec tasks?

Run the verification workflow to assess the selected change and generate a structured verification report. This report highlights CRITICAL, WARNING, and SUGGESTION issues with actionable recommendations for unaddressed tasks.

What is the best way to audit design coherence across code and design docs?

Coherence assessment audits design decisions and coding patterns for consistency across the project. It reviews code, tests, and design docs together to identify incoherent patterns and generate actionable recommendations.