How do I install the Openspec Continue Change skill?

Run npx skillmds@latest add redhat-developer/openspec-continue-change in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Openspec Continue Change safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Openspec Continue Change?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Openspec Continue Change free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Openspec Continue Change?

redhat-developer (@redhat-developer) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Openspec Continue Change by redhat-developer

Name: Openspec Continue Change
Author: redhat-developer

Openspec Continue Change

Creates exactly the next ready OpenSpec artifact for a change, one at a time — proposal, then specs or design (siblings), then tasks. Use for "what's the next artifact", "create the next artifact", "draft the next OpenSpec file", or when the user wants to progress artifacts step by step rather than generating everything at once. Stops after one artifact. Does not implement code.

redhat-developer 66f29af 2 files · 2.6 KB Updated Sep 17, 2026

File contents

Continue an OpenSpec change

Create one artifact — the next one whose dependencies are satisfied — and stop, so the user reviews each step before the next is generated.

Steps

Select the change. If not named or inferable from context, run openspec list --json and ask the user to pick from the most recently modified 3-4 changes, marking the most recent as "(Recommended)". Never guess.
Check status:
```
openspec status --change "<name>" --json
```
Read schemaName, artifacts[].status, and isComplete. Specs and design each depend only on proposal — when both are ready, pick one (either order is valid); do not treat YAML list order as a hard dependency.
Act on status:
- All complete (isComplete: true) — congratulate, show final status, suggest implementing (/openspec-apply-change) or archiving (/openspec-archive-change). Stop.
- An artifact is ready — pick one ready artifact and create it by following the artifact creation loop in /rhdh-spec-driven-schema. Create exactly one artifact, then stop.
- Nothing is ready and nothing is complete — this should not happen with a valid schema; show status and suggest checking for a schema issue.
Show progress: openspec status --change "<name>".

Output

After each invocation: which artifact was created, the schema in use, current progress (N/M complete), and what is now unlocked. Close with: "Want to continue? Just ask me to continue or tell me what to do next."

Guardrails

Create exactly one artifact per invocation — never more.
Never skip required dependencies; when multiple artifacts are ready (specs and design after proposal), either order is fine.
If context for the artifact is unclear, ask before creating it.

Completion

Complete when exactly one artifact was written (verified to exist on disk) and the user has seen updated progress and what it unlocked — or, if already complete, when that state was reported without attempting a write.

---name: openspec-continue-changedescription: Creates exactly the next ready OpenSpec artifact for a change, one at a time — proposal, then specs or design (siblings), then tasks. Use for "what's the next artifact", "create the next artifact", "draft the next OpenSpec file", or when the user wants to progress artifacts step by step rather than generating everything at once. Stops after one artifact. Does not implement code.---# Continue an OpenSpec changeCreate one artifact — the next one whose dependencies are satisfied — andstop, so the user reviews each step before the next is generated.## Steps1. **Select the change.** If not named or inferable from context, run `openspec list --json` and ask the user to pick from the most recently modified 3-4 changes, marking the most recent as "(Recommended)". Never guess.2. **Check status:** ```bash openspec status --change "<name>" --json ``` Read `schemaName`, `artifacts[].status`, and `isComplete`. Specs and design each depend only on proposal — when both are `ready`, pick one (either order is valid); do not treat YAML list order as a hard dependency.3. **Act on status:** - **All complete (`isComplete: true`)** — congratulate, show final status, suggest implementing (`/openspec-apply-change`) or archiving (`/openspec-archive-change`). Stop. - **An artifact is `ready`** — pick one ready artifact and create it by following the artifact creation loop in `/rhdh-spec-driven-schema`. Create exactly one artifact, then stop. - **Nothing is ready and nothing is complete** — this should not happen with a valid schema; show status and suggest checking for a schema issue.4. **Show progress:** `openspec status --change "<name>"`.## OutputAfter each invocation: which artifact was created, the schema in use, currentprogress (N/M complete), and what is now unlocked. Close with: "Want tocontinue? Just ask me to continue or tell me what to do next."## Guardrails- Create exactly one artifact per invocation — never more.- Never skip required dependencies; when multiple artifacts are ready (specs and design after proposal), either order is fine.- If context for the artifact is unclear, ask before creating it.## CompletionComplete when exactly one artifact was written (verified to exist on disk)and the user has seen updated progress and what it unlocked — or, if alreadycomplete, when that state was reported without attempting a write.

Frequently asked questions