agentleFS
Sign inStart free
redhat-developerredhat-developer/rhdh-skills/skills/refinement/openspec-continue-change/SKILL.md

openspec-continue-change

Skill20 starsChanged 20 days agoApache-2.0View on GitHub

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.

65 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use draft-openspec-docs, release-openspec and 5 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • goernSkill

    draft-openspec-docs

    Collaborative page-drafting mode for the OpenSpec docs. Builds a scratch plan inside the target page (purpose, structure, numbered draft steps), iterates on it with the user, then drafts one section per approved step and cleans up after itself. Use when a page needs a from-scratch rewrite or a new page is being shaped with the user in the loop.

    Also in 3 projects that use this

  • goernSkill

    release-openspec

    Use this skill when releasing OpenSpec: audit merged work and changeset coverage, decide whether a catch-up changeset PR is needed, prepare or resume the Changesets Version Packages PR, cut a beta or stable release, verify publishing, and polish GitHub release notes. Also use when asked whether an open release PR is complete, what the next release step is, or to continue a release paused for human approval.

    Also in 3 projects that use this

  • Microsoft AzureSkill

    openspec-update-change

    Update an OpenSpec change by revising its existing planning artifacts and keeping them coherent with one another. Use when the user wants to revise a change's plan, fold new decisions into it, or reconcile its artifacts after an edit. Never edits code.

    Also in 11 projects that use this

  • VercelSkill

    vercel-react-best-practices

    React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.

    Also in 3 projects that use this

  • MicrosoftSkill

    release

    Use ONLY when the user explicitly asks to cut/publish a Huabu desktop release or tag a version. Performs an outward action — bumps the version in apps/desktop/package.json, commits + annotated-tags vX.Y.Z, and pushes the branch + tag. That tag push auto-builds the macOS/Windows installers and publishes a GitHub Release. Provides `status`, `bump`, `tag-push`, and a one-command `run` (bump → tag-push).

    Also in 3 projects that use this

  • +2 more from goern

The file

We split this skill into the rules it gives an agent

8 rules. 2 are common, 4 are distinctive, and 2 are very specific to this project.

  • 2

    Common

    Most of the 63 edited versions we read keep these.

  • 4

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

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

    line 15
  2. Very specific:

    Select the change: If not named or inferable from context, run openspec list --json and ask the user to pick from the most recently …

    line 20
  3. Very specific:

    Read schemaName, artifacts[].status, and isComplete.

    line 30
  4. Distinctive:

    Create exactly one artifact, then stop.

    line 39
  5. Distinctive:

    After each invocation: which artifact was created, the schema in use, current progress (N/M complete), and what is now unlocked.

    line 47
  6. Common:

    Create exactly one artifact per invocation — never more.

    line 53
  7. Distinctive:

    Never skip required dependencies.

    line 54
  8. Common:

    If context for the artifact is unclear, ask before creating it.

    line 56

“Common” is measured: kept by at least 6 in 10 of the 63 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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

  1. 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:

    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>".

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.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free