skills.rest
dshearer
dshearerCOMMUNITY
Explore all skills by this author →
GitHub

openspec-continue-change

Generate the next OpenSpec change artifact via the openspec CLI.

2|Updated Feb 5, 2026
Search Tags:#workflow#specification#cli#openspec#artifact#change-management
One-click install
npx skills add https://github.com/dshearer/misatay --skill openspec-continue-change-dshearer
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-continue-change
Source: https://github.com/dshearer/misatay/tree/main/.claude/skills/openspec-continue-change
Command: npx skills add https://github.com/dshearer/misatay --skill openspec-continue-change-dshearer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Continue working on an OpenSpec change by creating the next artifact, streamlining collaboration and ensuring a consistent progression through the spec workflow.

Core Features & Use Cases

  • Guided continuation: select or infer the next artifact in an OpenSpec change and generate it according to the schema's rules.
  • Status-aware workflow: checks current artifacts, dependencies, and completion state to determine what can be created next.
  • Artifact creation guardrails: enforces single-artifact-per-invocation and orders artifacts properly, while integrating with dependency artifacts for context.

Quick Start

Ask me to continue the OpenSpec change to generate 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 continue an OpenSpec change and generate the next artifact?▼

To continue an OpenSpec change, the workflow automates selecting or inferring the next artifact, validates current status and dependencies, and writes the new artifact file to the prescribed path using the openspec CLI.

What is the artifact sequencing process in an OpenSpec workflow?▼

OpenSpec artifact sequencing enforces proper progression by checking completion state and dependencies, allowing only one artifact to be generated per invocation to maintain strict workflow order and schema compliance.

Do I need the openspec CLI to manage change artifacts?▼

Yes, this workflow interacts directly with the openspec CLI to list and describe changes, fetch instructions, and apply dependency context when generating the next artifact in the sequence.

Can I generate multiple artifacts for a change in a single step?▼

No, the workflow enforces a single-artifact-per-invocation guardrail to ensure proper sequencing, requiring you to continue the change iteratively for each subsequent artifact.

Why does my OpenSpec change workflow block artifact creation?▼

Artifact creation blocks when status validation detects incomplete dependencies or improper sequencing, ensuring you only generate artifacts that comply with the current change state and schema rules.

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
sachinnair90sachinnair90

openspec-continue-change

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

Community
Advanced
memorysavermemorysaver

openspec-ff-change

Generate OpenSpec change artifacts in dependency order via the openspec CLI.

Community
Advanced
luzhenqianluzhenqian
149

openspec-ff-change

Generate all OpenSpec artifacts for a specified change with dependency-aware sequencing.

Community
Advanced