skills.rest
circlebacknever
circlebackneverCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

openspec-continue-change

Creates the next required OpenSpec artifact from current change status and templates.

Updated Nov 29, 2022
Search Tags:#workflow#documentation#spec-driven#change management#openspec#artifact
One-click install
npx skills add https://github.com/circlebacknever/soundstage --skill openspec-continue-change-circlebacknever
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-continue-change
Source: https://github.com/circlebacknever/soundstage/tree/main/.codex/skills/openspec-continue-change
Command: npx skills add https://github.com/circlebacknever/soundstage --skill openspec-continue-change-circlebacknever

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you continue an OpenSpec-driven change without losing workflow state, so you can create the next required artifact in the correct order.

Core Features & Use Cases

  • Change Continuation: Determines the current status of a selected change and identifies what can be created next.
  • Artifact Creation: Produces the next required OpenSpec artifact using the schema-specific instructions and template.
  • Workflow Control: Stops after one artifact, preserving sequence and avoiding skipped steps.
  • Use Case: A developer has finished a proposal and wants the next OpenSpec document generated correctly without manually checking the workflow.

Quick Start

Use this skill to continue the selected OpenSpec change and create the next required 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 continue an OpenSpec change and generate the next artifact?▼

You maintain OpenSpec workflow state by generating exactly one artifact at a time, ensuring the next required proposal, spec, design, or task document is created in the correct sequence without skipping steps.

What is spec-driven change management and how does artifact sequencing work?▼

Spec-driven change management structures development into sequential artifacts. This Skill enforces artifact sequencing by reading OpenSpec status metadata and producing only the next required proposal, spec, design, or task document.

Why does my OpenSpec workflow skip documents when generating artifacts?▼

You avoid skipped workflow steps by using a skill that stops after creating exactly one required artifact, ensuring your OpenSpec change sequence remains strictly enforced without manual intervention.

Do I need to manually check OpenSpec status before creating the next spec document?▼

You do not need to manually check OpenSpec status, because this Skill automatically reads the status and instruction metadata to identify and generate the next required spec, proposal, design, or task document.

Can I automate proposal, spec, design, and task document creation for OpenSpec changes?▼

You can automate OpenSpec artifact creation by running this Skill to sequentially generate proposals, specs, designs, and task documents, with the workflow stopping after each individual artifact is produced.

Related Skills

Explore More Software Engineering Skills→
pacaplanpacaplan
30

openspec-continue-change

Create the next required OpenSpec artifact based on current change status.

Community
Intermediate
g1331g1331
3

openspec-continue-change

Generate the next OpenSpec change artifact via the openspec CLI.

Community
Advanced
MomoChenisMeMomoChenisMe
1

speclink-archive

Archive completed changes in a Spec-Driven Development workflow using the Speclink CLI.

Community
Intermediate
LippyyDevLippyyDev
1

openspec-ff-change

Scaffold OpenSpec change artifacts in dependency order using status queries.

Community
Advanced