Openspec Apply Change
Implement tasks from an OpenSpec change. Use when the user wants to start implementing, continue implementation, or work through tasks.
Install
npx skills add rpamis/comet --skill openspec-apply-changegit 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-changePersonal 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
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
Brainstorming
3.3krpamis/comet
Transforms rough ideas into fully-formed designs. Structure your brainstorming sessions and develop ideas systematically.
Dispatching Parallel Agents
3.3krpamis/comet
Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies
Finishing a Development Branch
3.3krpamis/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
Openspec Archive Change
3.3krpamis/comet
Archive a completed change in the experimental workflow. Use when the user wants to finalize and archive a change after implementation is complete.
Comet Tweak
3.3krpamis/comet
Use when 用户要进行可收敛为单一 OpenSpec change 的轻量或中等变更,且不需要完整设计;也用于恢复 tweak workflow。
Openspec Continue Change
3.3krpamis/comet
Continue working on an OpenSpec change by creating the next artifact. Use when the user wants to progress their change, create the next artifact, or continue their workflow.
Browse the most popular Claude skills, all productivity & notes skills, or write your own with the skills generator.