Openspec Apply Change

Implement tasks from an OpenSpec change. Use when the user wants to start implementing, continue implementation, or work through tasks.

3,306 stars 317 forksProductivity & Notes

Install

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add rpamis/comet --skill openspec-apply-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-apply-change ~/.claude/skills/openspec-apply-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

Implement tasks from an OpenSpec change.

**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 use the **AskUserQuestion tool** to let the user select

   Always announce: "Using change: <name>" and how to override (e.g., `/opsx:apply <other>`).

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 artifact contains the tasks (typically "tasks" for spec-driven, check status for others)

3. **Get apply instructions**

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

   This returns:
   - `contextFiles`: artifact ID -> array of concrete file paths (varies by schema - could be proposal/specs/design/tasks or spec/tests/implementation/docs)
   - Progress (total, complete, remaining)
   - Task list with status
   - Dynamic instruction based on current state

   **Handle states:**
   - If `state: "blocked"` (missing artifacts): show message, suggest using openspec-continue-change
Read the full skill on GitHub

Details

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

FAQ

What does the Openspec Apply Change skill do?

Implement tasks from an OpenSpec change. Use when the user wants to start implementing, continue implementation, or work through tasks.

How do I install the Openspec Apply Change skill?

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

Is Openspec Apply Change popular?

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

Related skills

Browse the most popular Claude skills, all productivity & notes skills, or write your own with the skills generator.