What is openspec-continue-change?

A workflow step for advancing an OpenSpec change by creating the next document that is ready. OpenSpec organizes software changes through artifacts such as proposals, specifications, designs, and task lists.

Continuing a change, selecting the next ready artifact, and creating or planning the next proposal, specification, design, or task document.

It keeps the change process moving one artifact at a time and prevents documentation work from turning into code implementation too early.

openspec-continue-change — Skill for Claude Code and Codex by chhuax

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 chhuax/praxis-devos --skill openspec-continue-change

Clone the repo

git clone --depth 1 https://github.com/chhuax/praxis-devos

Made for: Claude Code, Codex.

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/chhuax/praxis-devos/openspec-continue-change/github.svg)](https://agentmods.dev/skills/chhuax/praxis-devos/openspec-continue-change)

Your own site

<a href="https://agentmods.dev/skills/chhuax/praxis-devos/openspec-continue-change"><img src="https://agentmods.dev/badge/skills/chhuax/praxis-devos/openspec-continue-change/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/skills/chhuax/praxis-devos/openspec-continue-change"><img src="https://agentmods.dev/badge/skills/chhuax/praxis-devos/openspec-continue-change.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

When invoked 841 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.00043	$0.00841
Opus 5.5	$0.00017	$0.00336
Sonnet 5.5	$0.00009	$0.00168
Haiku 4.5	$0.00004	$0.00084

Measured 2mo ago against content hash 17cff63bbc89, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

openspec-continue-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 2mo 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.

assets/openspec/workflows/openspec-continue-change/SKILL.md · 118 lines

How it starts

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

Continue an OpenSpec change, but create only the next ready artifact each time.

Core Positioning

OpenSpec owns change selection, artifact dependencies, status, and instructions
Superpowers owns requirement convergence and task decomposition
Advance only one artifact at a time
The continue stage does not implement business code

Exact Skill Protocol

When this route is matched, you must call the corresponding exact skill name
Do not substitute a similar local skill, todo list, manual breakdown, or long-form reasoning
If the exact skill is unavailable, report that explicitly and pause the current routing

Capability Routing

If the current artifact depends on unclear goals, boundaries, or approaches, use superpowers:brainstorming first
If the current artifact is tasks.md, call superpowers:writing-plans by default
In the continue stage, writing-plans only serves the entire tasks.md
Do not generate docs/superpowers/plans/... or any extra master plan

Input

You may specify a change name. If none is given, first determine which change should be continued.

Execution Steps

1. Select the change

If the user provided a change name, use it directly
Otherwise, run openspec list --json
If multiple candidates exist, do not guess; let the user choose

2. Check status

Run:

openspec status --change "<name>" --json

Read:

schemaName
artifacts
isComplete

If isComplete: true, show the final status and stop.

3. Choose the current ready artifact

If any artifact has status: "ready", create only the first one
If there is no ready artifact, show the current status and explain that progress cannot continue yet

4. Read instructions and generate the artifact

Run:

openspec instructions <artifact-id> --change "<name>" --json

Then:

Read dependency artifacts
Write the file using the template structure
Treat context and rules as constraints
Do not copy those constraint blocks verbatim into the artifact

Read the full file on GitHub · 118 lines

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.

2mo ago First seen · 118 lines · 43 tokens per session scan A 17cff63bbc89

Subscribe to this mod's changes

openspec-continue-change is a skill published in the GitHub repository chhuax/praxis-devos (21 stars, last pushed 6mo ago), licensed Apache-2.0. It adds 43 tokens to every session and 841 once invoked, about $0.0002 per session on Opus 5.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

openspec-continue-change next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
openspec-continue-changechhuax/praxis-devos	Skill	21	6mo ago	Apache-2.0	A	43	Claude Code, Codex
imagegenopenai/codex	Skill	133k	yesterday	Apache-2.0	A	113	Codex
playwright-climicrosoft/playwright	Skill	99k	yesterday	Apache-2.0	A	19	Claude Code
local-ai-agentsmicrosoft/ai-agents-for-beginners	Skill	79k	4d ago	MIT	A	200	Claude Code, Codex
systematic-debuggingobra/superpowers	Skill	313k	3d ago	MIT	A	21	Claude Code
next-cache-components-adoptionvercel/next.js	Skill	143k	yesterday	MIT	A	95	Claude Code
next-partial-prefetching-adoptionvercel/next.js	Skill	143k	yesterday	MIT	A	103	Claude Code