openspec-verify-change

Verify implementation alignment with specs, tasks, and design artifacts.

273|270|Updated Jun 30, 2025
One-click install
npx skills add https://github.com/LIDR-academy/AI4Devs-LTI-extended --skill openspec-verify-change-lidr-academy
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-verify-change
Source: https://github.com/LIDR-academy/AI4Devs-LTI-extended/tree/main/.cursor/skills/openspec-verify-change
Command: npx skills add https://github.com/LIDR-academy/AI4Devs-LTI-extended --skill openspec-verify-change-lidr-academy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps engineering teams ensure that a given implementation precisely reflects the change artifacts (specs, tasks, and design) before the artifact is archived, preventing drift and misalignment.

Core Features & Use Cases

  • Comprehensive completeness checks: validates task completion and spec coverage against delta artifacts.
  • Correctness validation: maps requirements to code and detects divergences.
  • Coherence assessment: evaluates design adherence and pattern consistency.
  • Generates a structured verification report with actionable recommendations.

Quick Start

Provide the change name to verify, or let the system prompt you to select from available 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 implementation completeness against change artifacts before archiving?

To verify implementation completeness, validate task completion and spec coverage against delta artifacts by parsing context files and extracting task status from tasks.md to ensure alignment before archiving.

What is change artifact validation and how does it prevent spec drift?

Change artifact validation checks that an implementation precisely reflects specs, tasks, and design documents, preventing drift by mapping requirements to code and detecting divergences before the artifact is archived.

How do I check if my code conforms to openspec design documents and task definitions?

Check code conformity by scanning context artifacts, analyzing tasks.md for task status, and validating spec requirements against design.md to determine coverage and pattern consistency.

Can I generate a verification report with a prioritized issue list for delta changes?

Yes, you can generate a committed verification report with a prioritized issue list by validating spec requirements, extracting task status, and assessing coherence across delta changes.

Does openspec verification work without external dependencies for quality assurance?

Yes, openspec verification operates without external dependencies, running comprehensive completeness checks and correctness validation directly against your local context artifacts and change files.

What is the best way to assess design adherence and pattern consistency during code review?

Assess design adherence by evaluating the implementation against change artifacts, specifically analyzing design.md and spec definitions to detect divergences and ensure pattern consistency throughout the build process.