skills.rest
Rushtu99
Rushtu99COMMUNITY
Explore all skills by this author →
GitHub

openspec-continue-change

Create the next OpenSpec artifact using status-checked progression.

Updated Mar 30, 2026
Search Tags:#automation#workflow#cli#openspec#artifact#change
One-click install
npx skills add https://github.com/Rushtu99/Codex-ReVamped --skill openspec-continue-change-rushtu99
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-continue-change
Source: https://github.com/Rushtu99/Codex-ReVamped/tree/main/.agents/skills/openspec-continue-change
Command: npx skills add https://github.com/Rushtu99/Codex-ReVamped --skill openspec-continue-change-rushtu99

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Continue OpenSpec changes by providing a guided workflow to advance a change to the next artifact.

Core Features & Use Cases

  • Progressive change management through artifact sequencing using the OpenSpec CLI.
  • Dependency-aware artifact creation and status-driven progression.
  • Guardrails and prompts to ensure correct ordering and safe execution.

Quick Start

Run the openspec continue-change command and follow prompts to advance the selected change to the next artifact.

Frequently Asked Questions about openspec-continue-change

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I advance an OpenSpec change to the next artifact?▼

To advance an OpenSpec change, run the openspec continue-change command and follow the prompts to progress the selected change to the next artifact using the provided template.

What is artifact sequencing in OpenSpec workflows?▼

Artifact sequencing in OpenSpec workflows is the process of breaking changes into sequential artifacts that require status-checked progression before the next artifact is created and written to a specified location.

Does the OpenSpec continue-change workflow require the openspec CLI?▼

Yes, the OpenSpec continue-change workflow satisfies a dependency on the openspec CLI, using it to read artifact status and ensure dependency-aware progression for safe execution.

How does status-driven progression work for OpenSpec artifacts?▼

Status-driven progression works by reading the current artifact status via the openspec CLI, applying guardrails and prompts to ensure correct ordering, and then writing the next artifact to continue the change.

Can I use continue-change to skip artifacts in an OpenSpec workflow?▼

No, continue-change enforces dependency-aware artifact creation with guardrails and prompts to ensure correct ordering, preventing users from skipping sequential artifacts in the workflow.

Related Skills

Explore More Software Engineering Skills→
SAPSAP
221

openspec-continue-change

Create the next OpenSpec artifact using the OpenSpec CLI.

Official
Advanced
Charles5277Charles5277
45

openspec-continue-change

Generate the next OpenSpec change artifact according to the current schema.

Community
Advanced
MeetTechnologyMeetTechnology

openspec-continue-change

Automate OpenSpec change progression by generating the next artifact via CLI.

Community
Advanced
moogahmoogah

opsx-ff

Scaffold software change artifacts in dependency order under openspec/changes.

Community
Advanced