What is openspec-apply-change?

A workflow for applying an OpenSpec change—a documented software change with a proposal, specifications, design, and task checklist—to real code.

Use it to start or continue implementing an OpenSpec change, work through its tasks one at a time, and stop when everything is done or blocked.

It keeps implementation tied to the agreed design and makes progress visible by checking off tasks only after they are complete. It also identifies when required documents are missing or work is blocked.

openspec-apply-change — Skill for Claude Code and Codex by redhat-deve

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent

npx skills add redhat-developer/rhdh-skills --skill openspec-apply-change

Clone the repo

git clone --depth 1 https://github.com/redhat-developer/rhdh-skills

Made for: Claude Code, Codex.

Or install refinement, the plugin that ships this one along with the rest of its 13 skills.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/skills/redhat-developer/rhdh-skills/openspec-apply-change.svg)](https://agentmods.dev/skills/redhat-developer/rhdh-skills/openspec-apply-change)

Your own site

<a href="https://agentmods.dev/skills/redhat-developer/rhdh-skills/openspec-apply-change"><img src="https://agentmods.dev/badge/skills/redhat-developer/rhdh-skills/openspec-apply-change.svg" alt="Measured on agentmods" height="20"></a>

Per session 98 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 884 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00098	$0.00884
Opus 5	$0.00049	$0.00442
Sonnet 5	$0.00020	$0.00177
Haiku 4.5	$0.00010	$0.00088

Measured 6d ago against content hash 2e64df414a8c, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade A, and why

openspec-apply-change scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 6d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

skills/refinement/openspec-apply-change/SKILL.md · 78 lines

How it starts

The opening of the file, as written. The whole thing — 78 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Implement OpenSpec change tasks

Work through a change's task checklist against real code, one task at a time, checking each off only once it is actually done.

Steps

Select the change. Use a given name; otherwise infer from context, or auto-select if only one active change exists. If ambiguous, run openspec list --json and let the user choose. Always announce which change is in use.
Check status: openspec status --change "<name>" --json — read schemaName and which artifact holds the tasks.
Get apply instructions:
```
openspec instructions apply --change "<name>" --json
```
Returns contextFiles (artifact ID -> file paths), task progress, the task list with status, and a dynamic instruction. If state: "blocked" (missing artifacts), suggest /openspec-continue-change. If state: "all_done", congratulate and suggest /openspec-archive-change.
Read every file listed under contextFiles before starting — for rhdh-spec-driven that is proposal, specs, design, and tasks.
Choose an execution mode for this run, per /rhdh-spec-driven-schema's schema.yaml apply block: direct mode for mechanical, low-risk work; team mode (implementer + independent verifier subagents) for semantically complex, ADR-bound, or broad cross-layer work. Announce the choice and rationale before making changes; do not silently switch mid-run.
Work through pending tasks until done or blocked: show which task is active, make minimal focused changes, flip - [ ] to - [x] immediately on completion, continue to the next task. Pause on an unclear task, a design issue surfaced by implementation, an error, or user interruption.
Journal as you go, invoking /openspec-journal: mode.chosen once at start, task.start/task.complete per task (or per assigned range in team mode), verifier.result per verdict in team mode, task.blocked on pause, decision for load-bearing calls, handoff as the last line before stopping and the first line on resume. Also keep the default turn bookending (turn.start/turn.end) described there.
On completion or pause, show status: tasks completed this session, overall progress (N/M), and either a suggestion to archive or an explanation of the pause with options.

Read the full file on GitHub · 78 lines

Files

What ships with it

1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

agents/openai.yaml 141 B

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

6d ago First seen · 78 lines · 98 tokens per session scan A 2e64df414a8c

Subscribe to this mod's changes

openspec-apply-change is a skill published in the GitHub repository redhat-developer/rhdh-skills (16 stars, last pushed 3d ago), licensed Apache-2.0. It adds 98 tokens to every session and 884 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Planning

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens