What is openspec-ff-change?

An OpenSpec workflow that generates all required planning documents for a software change in one pass. OpenSpec is a system that organizes a proposal, requirements, design, and implementation tasks before coding begins.

Use it when you want to fast-forward a new or existing change through proposal, specifications, design, and task planning.

It removes the need to create each planning document manually and tracks the required order and dependencies. It then hands the prepared change to implementation.

openspec-ff-change — Skill for Claude Code and Codex by redhat-developer: An OpenSpec workflow that generates all required planning document

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.

agentmods

npx agentmods add skills/redhat-developer/rhdh-skills/openspec-ff-change

Any agent

npx skills add redhat-developer/rhdh-skills --skill openspec-ff-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-ff-change.svg)](https://agentmods.dev/skills/redhat-developer/rhdh-skills/openspec-ff-change)

Your own site

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

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

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

Security scan A 0 findings. Scan, not verified.

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.00080	$0.00764
Opus 5	$0.00040	$0.00382
Sonnet 5	$0.00016	$0.00153
Haiku 4.5	$0.00008	$0.00076

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

Security

Grade A, and why

openspec-ff-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-ff-change/SKILL.md · 72 lines

How it starts

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

Fast-forward an OpenSpec change

Generate every artifact the schema requires before implementation can start, without pausing between them, then hand off to implementation.

Steps

Ensure the project schema is installed. Check whether openspec/config.yaml and openspec/schemas/rhdh-spec-driven/ already exist. Only if either is missing, invoke /rhdh-spec-driven-schema and run its project-install step. Then confirm with openspec schemas --json.
Get the change name or description. Derive a kebab-case name from a description if no name was given (e.g. "add user authentication" -> add-user-auth); do not proceed without knowing what to build.
Create the change directory (skip if it already exists — see Guardrails): openspec new change "<name>" (default schema from openspec/config.yaml, or pass --schema rhdh-spec-driven).
Get the build order:
```
openspec status --change "<name>" --json
```
Read applyRequires (artifact IDs needed before implementation) and artifacts (status + dependencies for each). Specs and design are siblings: after proposal, either may be ready; create them in either order once their dependencies are satisfied.
Create every required artifact in dependency order. Track progress with TodoWrite. For each artifact whose dependencies are satisfied, follow the artifact creation loop in /rhdh-spec-driven-schema — read dependencies, use the template, apply context/rules without copying them into the file, write to outputPath. Re-check status after each write; stop once every ID in applyRequires reports status: "done".
If an artifact needs input the description didn't cover, ask — but prefer a reasonable default to keep momentum; this skill exists to avoid stopping between artifacts.
Show final status: openspec status --change "<name>".

Output

Change name and location, every artifact created with a one-line description, "All artifacts created! Ready for implementation.", and: "Run /openspec-apply-change to start working on the tasks."

Read the full file on GitHub · 72 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 158 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 · 72 lines · 80 tokens per session scan A 90016e9f8aeb

Subscribe to this mod's changes

openspec-ff-change is a skill published in the GitHub repository redhat-developer/rhdh-skills (16 stars, last pushed 2d ago), licensed Apache-2.0. It adds 80 tokens to every session and 764 once invoked, about $0.0004 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 Writing and docs

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