Openspec Verify Change

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.

Project check: These steps expect a project that already uses OpenSpec. Before the first step that writes anything (new change, archive, sync specs, or authoring an artifact file), confirm the project has a root: run openspec list --json (with --store <id> when a store is selected, since the store is then the root) and read root. A root object means the project is set up. "root": null means it is not - there is no openspec/ directory here, and a write such as openspec new change would create one as a side effect. The command also exits non-zero, which is that answer rather than a broken CLI, so read the JSON instead of retrying or working around it.

One "root": null is not about setup: when a status error message starts with Declared in or Invalid store declaration in and names this project's openspec/config.yaml (or config.yml), the project does use OpenSpec through a store it declares, which this machine cannot resolve (the store is not registered, or the store: line is malformed). Do not treat it as uninitialized and skip the branches below: stop before writing and show the user that error's message and fix.

Otherwise, with no root, what happens next depends on how this workflow was reached:

• Auto-selected: you chose this workflow yourself, without the user naming OpenSpec, naming this skill, or running its slash command. Stop using OpenSpec and answer the request normally, as you would with no OpenSpec installed. Do not ask them to set anything up and do not mention OpenSpec setup.
• Explicit OpenSpec request: the user named OpenSpec, named this skill, or ran its slash command. Stop before writing and ask how to proceed: set this project up (openspec init), target a store they already have (--store <id>), or continue without OpenSpec for this request. Wait for their answer.

In both branches, never create the root as a side effect: do not run openspec init until the user asks for it, do not hand-create openspec/ files, and do not let a command create it.

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: <name>" and how to override (e.g., /openspec-verify-change <other>).

1. Check status to understand the schema ``bash 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

1. 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.

1. 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.

1. Verify Completeness

Task Completion:

• If contextFiles.tasks exists, read every file path in it
• Parse checkboxes: complete means the box holds only x/X, ignoring spacing (- [ x] is complete); every other marker is incomplete (- [ ], - [], and unfamiliar ones such as - [~] or - [-])
• Count complete vs total tasks
• If incomplete tasks exist:
• Add CRITICAL issue for each incomplete task
• Recommendation: "Complete task: <description>" or "Mark as done if already implemented"

Spec Coverage:

• If delta specs exist in contextFiles.specs:
• Extract all requirements (marked with "### Requirement:")
• For each requirement:
• Search codebase for keywords related to the requirement
• Assess if implementation likely exists
• If requirements appear unimplemented:
• Add CRITICAL issue: "Requirement not found: <requirement name>"
• Recommendation: "Implement requirement X: <description>"

1. Verify Correctness

Requirement Implementation Mapping:

• For each requirement from delta specs:
• Search codebase for implementation evidence
• If found, note file paths and line ranges
• Assess if implementation matches requirement intent
• If divergence detected:
• Add WARNING: "Implementation may diverge from spec: <details>"
• Recommendation: "Review <file>:<lines> against requirement X"

Scenario Coverage:

• For each scenario in delta specs (marked with "#### Scenario:"):
• Check if conditions are handled in code
• Check if tests exist covering the scenario
• If scenario appears uncovered:
• Add WARNING: "Scenario not covered: <scenario name>"
• Recommendation: "Add test or implementation for scenario: <description>"

1. Verify Coherence

Design Adherence:

• If contextFiles.design exists:
• Extract key decisions (look for sections like "Decision:", "Approach:", "Architecture:")
• Verify implementation follows those decisions
• If contradiction detected:
• Add WARNING: "Design decision not followed: <decision>"
• Recommendation: "Update implementation or revise design.md to match reality"
• If no design.md: Skip design adherence check, note "No design.md to verify against"

Code Pattern Consistency:

• Review new code for consistency with project patterns
• Check file naming, directory structure, coding style
• If significant deviations found:
• Add SUGGESTION: "Code pattern deviation: <details>"
• Recommendation: "Consider following project pattern: <example>"

1. Generate Verification Report

Summary Scorecard:

   ## Verification Report: <change-name>

   ### Summary
   | Dimension    | Status           |
   |--------------|------------------|
   | Completeness | X/Y tasks, N reqs|
   | Correctness  | M/N reqs covered |
   | Coherence    | Followed/Issues  |

Issues by Priority:

1. CRITICAL (Must fix before archive):

• Incomplete tasks
• Missing requirement implementations
• Each with specific, actionable recommendation