Openspec Verify Change

Verify implementation matches change artifacts. Use when the user wants to validate that implementation is complete, correct, and coherent before archiving.

3,306 stars 317 forksOther

Install

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add rpamis/comet --skill openspec-verify-change
Manual install
git clone --depth 1 https://github.com/rpamis/comet.git /tmp/comet
mkdir -p ~/.claude/skills
cp -r /tmp/comet/eval/local/skills/benchmarks/dependency/openspec/openspec-verify-change ~/.claude/skills/openspec-verify-change

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

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

**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. **If no change name provided, prompt for selection**

   Run `openspec list --json` to get available changes. Use the **AskUserQuestion tool** to let the user select.

   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)".

   **IMPORTANT**: Do NOT guess or auto-select a change. Always let the user choose.

2. **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")
   - Which artifacts exist for this change

3. **Get the change directory and load artifacts**

   ```bash
   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
Read the full skill on GitHub

Details

Skill name
openspec-verify-change
Repository
rpamis/comet
Path
eval/local/skills/benchmarks/dependency/openspec/openspec-verify-change/SKILL.md
License
MIT
Repo updated
18 November 2026

FAQ

What does the Openspec Verify Change skill do?

Verify implementation matches change artifacts. Use when the user wants to validate that implementation is complete, correct, and coherent before archiving.

How do I install the Openspec Verify Change skill?

skills CLI (Claude Code, Cursor, Codex and more): npx skills add rpamis/comet --skill openspec-verify-change. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Openspec Verify Change popular?

It lives in rpamis/comet, which has 3,306 GitHub stars and 317 forks.

Related skills

Brainstorming

3.3k

rpamis/comet

Transforms rough ideas into fully-formed designs. Structure your brainstorming sessions and develop ideas systematically.

AI, LLMs & AgentsIn 2 lists317

Dispatching Parallel Agents

3.3k

rpamis/comet

Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies

AI, LLMs & AgentsIn 2 lists317

Finishing a Development Branch

3.3k

rpamis/comet

Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup

Git & Code ReviewIn 2 lists317

Problem Solving

2.2k

mrgoonie/claudekit-skills

Creative problem-solving techniques for breaking through stuck points - includes collision-zone thinking, inversion, pattern recognition, and simplification

Other418

Openspec Sync Specs

3.3k

rpamis/comet

Sync delta specs from a change to main specs. Use when the user wants to update main specs with changes from a delta spec, without archiving the change.

Other317

Sw Character Conflict

2.1k

jtydhr88/screenwriting-skills

Character creation, protagonist/antagonist design and dramatic conflict for scripts (人物/对手/冲突) — merged from Lajos Egri (three-dimensional character, orchestration, unity of opposites, pivotal character, rising vs static vs jumping conflict, transition), William Indick's Psychology for Screenwriters (Freud, Erikson, Jung archetypes, Campbell/Murdock hero journeys, Adler, Rollo May), Robert McKee (characterization vs true character, dimensions, gap, antagonism principle), Neill Hicks (character invocation, self-concept, cognitive dissonance, five conflict focuses, Maslow), Lisa Cron (desire vs

Other220

Browse the most popular Claude skills, all other skills, or write your own with the skills generator.