openspec-verify-change

Verify openspec-tracked changes against tasks, delta specs, and design artifacts.

Updated Dec 25, 2025
One-click install
npx skills add https://github.com/wtg42/tty-clock-timer --skill openspec-verify-change-wtg42
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-verify-change
Source: https://github.com/wtg42/tty-clock-timer/tree/main/.opencode/skills/openspec-verify-change
Command: npx skills add https://github.com/wtg42/tty-clock-timer --skill openspec-verify-change-wtg42

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill validates that an implementation matches its change artifacts (tasks, delta specs, and design) so incomplete or divergent work is caught before a change is archived.

Core Features & Use Cases

  • Guided change selection: enumerates openspec changes with implementation tasks and prompts the user to choose the correct change.
  • Completeness checks: parses task checklists and marks incomplete tasks as CRITICAL with actionable recommendations.
  • Correctness mapping: extracts requirements from delta specs and searches the repository for implementation evidence with file references and line hints.
  • Coherence review: compares implementation against design decisions and flags deviations or pattern inconsistencies.
  • Use case: run prior to archiving a change to produce a prioritized Verification Report (CRITICAL/WARNING/SUGGESTION) and actionable remediation steps.

Quick Start

Use openspec-verify-change to verify the change named my-change and generate a completeness, correctness, and coherence verification report before archiving.

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 against openspec change artifacts before archiving?

You can verify implementation against openspec change artifacts by parsing task checklists, extracting delta spec requirements, and searching repository code for compliance evidence to generate a prioritized verification report.

What is spec compliance verification for code review?

Spec compliance verification checks whether implementation matches change artifacts by mapping delta spec requirements to code evidence, reviewing coherence against design decisions, and flagging incomplete tasks before archiving.

How do I check openspec task completeness and correctness in my repository?

Check openspec task completeness by parsing task checklists to find incomplete items, then verify correctness by extracting requirements from delta specs and searching repository context for implementation evidence with file references.

Can I use openspec-verify-change without the openspec CLI installed?

No, spec compliance verification requires the openspec CLI to list changes, inspect change status, retrieve contextFiles, and perform task parsing and code-to-requirement evidence searches.

What does a pre-archive verification report include for openspec changes?

A pre-archive verification report includes completeness checks, correctness mapping with file references and line hints, and coherence reviews, prioritized as CRITICAL, WARNING, or SUGGESTION with actionable remediation steps.

When should I run change artifact validation for spec compliance?

Run change artifact validation prior to archiving an openspec-tracked change to catch incomplete or divergent work, ensuring implementation matches tasks, delta specs, and optional design decisions.