openspec-verify-change

Verify OpenSpec implementations against change artifacts and generate a markdown report.

Updated Nov 12, 2025
One-click install
npx skills add https://github.com/artagon/artagon-vscode-profiles --skill openspec-verify-change-artagon
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-verify-change
Source: https://github.com/artagon/artagon-vscode-profiles/tree/main/agents/skills/openspec-verify-change
Command: npx skills add https://github.com/artagon/artagon-vscode-profiles --skill openspec-verify-change-artagon

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires openspec-cli.

What problem does it solve?

This Skill prevents incomplete or incorrect implementations by verifying that code and artifacts still match the corresponding OpenSpec change package you plan to archive.

Core Features & Use Cases

  • Change-to-artifact verification: Lists available changes, selects the correct one, and loads the change directory plus context files (tasks, specs, design) for validation.
  • Completeness checks: Evaluates task checkboxes for completion status and checks whether spec requirements appear implemented in the codebase.
  • Correctness and coherence checks: Flags likely divergences between implemented code and requirement intent, assesses scenario coverage (code and tests), and verifies design adherence when design artifacts exist.

Quick Start

Ask the Skill to verify an OpenSpec change by name, or let it infer none and prompt you to choose from available changes, then produce a structured verification report with prioritized issues.

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 spec compliance before archiving an OpenSpec change?

To verify spec compliance, the Skill checks your change directory against tasks, delta specs, and design artifacts using openspec CLI. It produces a prioritized CRITICAL/WARNING/SUGGESTION markdown report flagging incomplete implementations.

What is scenario coverage verification in a spec-driven workflow?

Scenario coverage verification assesses whether spec requirements are fully implemented in code and tests. It flags divergences between implemented code and requirement intent to ensure completeness and correctness before archiving.

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

Check implementation matches by loading the change directory plus context files. The Skill evaluates task checkbox completion, verifies design adherence, and flags likely divergences between code and requirement intent.

Do I need openspec-cli installed to run pre-archive checks?

Yes, openspec-cli is a required dependency. The Skill relies on openspec CLI discovery and status commands to load change artifacts and validate spec compliance before generating its verification report.

What is the best way to audit tasks and specs for an OpenSpec change package?

The best way to audit tasks and specs is to apply artifact loading across the change directory. The Skill evaluates task checkboxes, checks spec requirement implementation, and assesses scenario coverage for code and tests.

Why does my OpenSpec implementation report show CRITICAL warnings?

CRITICAL warnings appear when verification detects severe divergences between implemented code and requirement intent, incomplete task checkboxes, or missing scenario coverage. The report prioritizes issues to resolve before archiving the change.