openspec-verify-change

Verify implementation alignment with OpenSpec change artifacts and generate structured reports.

Updated Feb 4, 2026
One-click install
npx skills add https://github.com/SQDR2/PortableConversationScriptAssistant --skill openspec-verify-change-sqdr2
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-verify-change
Source: https://github.com/SQDR2/PortableConversationScriptAssistant/tree/main/.github/skills/openspec-verify-change
Command: npx skills add https://github.com/SQDR2/PortableConversationScriptAssistant --skill openspec-verify-change-sqdr2

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Verify that implementations align with change artifacts (specs, tasks, and design), preventing drift before archiving.

Core Features & Use Cases

  • Automates cross-artifact verification by correlating specs, tasks, and design with code.
  • Generates a structured verification report highlighting completeness, correctness, and coherence.
  • Supports actionable remediation notes with file/line references for rapid fixes.

Quick Start

Run the openspec-verify-change command to validate that an implementation matches the associated change artifacts.

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 specs and design artifacts?

To verify code changes against specs and design artifacts, run the openspec-verify-change command to correlate implementation files with change artifacts, producing a structured verification report detailing completeness, correctness, and coherence.

What is OpenSpec change verification in software projects?

OpenSpec change verification is a workflow that ensures traceability across specs, tasks, design artifacts, code, and tests, preventing drift by confirming that a given implementation satisfies the selected change requirements before archiving.

How do I check if my implementation matches change tasks and design docs?

To check if an implementation matches change tasks and design docs, apply the OpenSpec workflow to cross-reference artifacts with code, generating actionable remediation notes with file and line references for any mismatches found.

Does spec-validation work without integrating external testing frameworks?

Spec-validation through this workflow operates independently by analyzing artifact coherence and traceability within the project, generating a structured report without requiring integration of external testing frameworks or dependencies.

What's the best way to prevent drift before archiving software changes?

The best way to prevent drift before archiving is to automate cross-artifact verification by correlating specs, tasks, and design with code, yielding a report that highlights completeness and provides actionable remediation notes.

Why does my implementation verification report show coherence errors?

Implementation verification reports show coherence errors when the code lacks traceability across the associated spec, task, and design artifacts, requiring you to resolve the flagged file and line references for rapid fixes.