openspec-verify-change

name	openspec-verify-change
description	Verify implementation matches change artifacts. Use when the user wants to validate that implementation is complete, correct, and coherent before archiving.
allowed-tools	Bash(openspec:*), Bash(bun:*)
license	MIT
compatibility	Requires openspec CLI.
metadata	{"author":"openspec","version":"1.0"}

This repository (Asymmetric-al/core)

These repo-owned sections sit above the official OpenSpec skill. Reconcile this overlay after upstream refreshes before running bun run skills:sync.

Use the locally pinned CLI only: bun run openspec -- <command>. Do not invoke @latest. Core does not use Stores. Pass an explicit change ID before any mutating OpenSpec operation. Follow AGENTS.md and docs/ai/rules/openspec.md. Do not bypass TDD, exact base-maia, data-access boundaries, security, or repository checks. Do not archive unmerged or incomplete work. Do not run openspec update against the live customized repository. Do not treat product runtime Eve as a coding agent.

Allowed-tools metadata includes Bash(bun:*) so the local wrapper can run.

Triggers

• The matching OpenSpec workflow is requested: Explore, Propose, Update, Apply, Verify, Sync, or Archive.
• Numbered commands /1-start-project through /4-close-project wrap these workflows.

Workflow

1. Read openspec/config.yaml, openspec/project.md, and the relevant specs or active change.
2. Invoke bun run openspec -- with the explicit change ID for mutating work.
3. Keep Core TDD, UI, data-boundary, and Guardian rules in force.
4. Leave the change active until implementation has merged.

Checklist

• Local pinned CLI used via bun run openspec --
• Explicit change ID used for mutating operations
• Stores were not introduced
• Incomplete or unmerged work was not archived
• openspec update was not run against the live repo
• Product Eve was not treated as a coding agent

Verify that an implementation matches the change artifacts (specs, tasks, design).

Store selection: If the user names a store (a store is a standalone OpenSpec repo registered on this machine) or the work lives in one, run openspec store list --json to discover registered store ids, then pass --store <id> on the commands that read or write specs and changes (new change, status, instructions, list, show, validate, archive, doctor, context, schemas, view). Once selected, treat --store <id> as sticky for the rest of the workflow. Every unscoped example of those commands below is shorthand: before running it, append the flag. For example, run openspec status --change "<name>" --json --store "<id>", not the unscoped form shown below. Other commands do not take the flag. Hints printed by commands already carry the flag; keep it on follow-ups. Without a store, commands act on the nearest local openspec/ root.

Input: Optionally specify a change name. If omitted, check if it can be inferred from conversation context. If vague or ambiguous you MUST prompt for available changes.

Steps

1. Select the change

   If a name is provided, use it. Otherwise:

   • Infer from conversation context if the user mentioned a change
   • Auto-select if only one active change exists
   • If ambiguous, run openspec list --json to get available changes and ask the user to select one

   When prompting, show changes that have implementation tasks (tasks artifact exists). Include the schema used for each change if available. Mark changes with incomplete tasks as "(In Progress)".

   Always announce: "Using change: " and how to override (e.g., /openspec-verify-change <other>).

2. Check status to understand the schema

   openspec status --change "<name>" --json
   

   Parse the JSON to understand:

   • schemaName: The workflow being used (e.g., "spec-driven")
   • planningHome, changeRoot, artifactPaths, and actionContext: path and scope context
   • Which artifacts exist for this change

3. Get planning context and load artifacts

   openspec instructions apply --change "<name>" --json
   

   This returns the change directory and contextFiles (artifact ID -> array of concrete file paths). Read all available artifacts from contextFiles.

4. Initialize verification report structure

   Create a report structure with three dimensions:

   • Completeness: Track tasks and spec coverage
   • Correctness: Track requirement implementation and scenario coverage
   • Coherence: Track design adherence and pattern consistency

   Each dimension can have CRITICAL, WARNING, or SUGGESTION issues.

5. Verify Completeness

   Task Completion:

   • If contextFiles.tasks exists, read every file path in it
   • Parse checkboxes: - [ ] (incomplete) vs - [x] (complete)
   • Count complete vs total tasks
   • If incomplete tasks exist:

Verification Heuristics

• Completeness: Focus on objective checklist items (checkboxes, requirements list)
• Correctness: Use keyword search, file path analysis, reasonable inference - don't require perfect certainty
• Coherence: Look for glaring inconsistencies, don't nitpick style
• False Positives: When uncertain, prefer SUGGESTION over WARNING, WARNING over CRITICAL
• Actionability: Every issue must have a specific recommendation with file/line references where applicable

Graceful Degradation

• If only tasks.md exists: verify task completion only, skip spec/design checks
• If tasks + specs exist: verify completeness and correctness, skip design
• If full artifacts: verify all three dimensions
• Always note which checks were skipped and why

Output Format

Use clear markdown with:

• Table for summary scorecard
• Grouped lists for issues (CRITICAL/WARNING/SUGGESTION)
• Code references in format: file.ts:123
• Specific, actionable recommendations
• No vague suggestions like "consider reviewing"