skills.rest
remiverdiesen
remiverdiesenCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

openspec-continue-change

Create the next OpenSpec artifact for an in-progress change.

6|Updated Nov 21, 2025
Search Tags:#workflow#developer tools#spec-driven#change management#openspec#artifact
One-click install
npx skills add https://github.com/remiverdiesen/ark-fork --skill openspec-continue-change-remiverdiesen
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-continue-change
Source: https://github.com/remiverdiesen/ark-fork/tree/main/.claude/skills/openspec-continue-change
Command: npx skills add https://github.com/remiverdiesen/ark-fork --skill openspec-continue-change-remiverdiesen

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes the friction of resuming an in-progress OpenSpec change by guiding the next correct step instead of forcing you to remember workflow state, artifact order, or schema-specific requirements.

Core Features & Use Cases

  • Change Continuation: Picks up an existing OpenSpec change and moves it forward from the current status.
  • Artifact Sequencing: Checks what is ready, reads the required instructions, and creates exactly one next artifact in the proper order.
  • Workflow Support: Helps developers continue proposal, spec, design, or task creation without guessing what comes next.
  • Use Case: A teammate asks to continue a partially completed change, and this Skill determines the next artifact to create and writes it in the right location.

Quick Start

Ask the assistant to continue the specified 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 resume an in-progress OpenSpec change without remembering the workflow state?▼

To resume an OpenSpec change, you direct the assistant to continue the specified change. It reads the current status, checks artifact dependencies, and automatically generates the exact next required artifact in the correct sequence.

What is the best way to manage artifact sequencing for spec-driven development?▼

Spec-driven artifact sequencing is managed by applying schema-specific instructions and templates. The system checks what is ready, respects dependencies, and writes exactly one artifact per invocation to ensure proper workflow progression.

How do I create the next artifact for a partially completed change request?▼

Creating the next artifact for a partially completed change is done by invoking the continuation workflow. It evaluates existing progress and writes exactly one new artifact in the proper location without guessing the next step.

Does OpenSpec change continuation work with existing schema-specific templates?▼

OpenSpec change continuation works directly with existing schema-specific templates. It reads the required instructions for the target schema, respects template dependencies, and generates the next artifact in the correct format and location.

When should I not use an automated artifact sequencing workflow?▼

Automated artifact sequencing should not be used when you need to create multiple artifacts simultaneously. This workflow is designed to write exactly one artifact per invocation to strictly maintain dependency order and schema compliance.

Related Skills

Explore More Software Engineering Skills→
crozzbitecrozzbite

openspec-continue-change

Create the next OpenSpec change artifact based on schema and status.

Community
Advanced
jaxxstormjaxxstorm
4

openspec-continue-change

Create the next OpenSpec change artifact via the openspec CLI.

Community
Advanced
joannanowakowskajoannanowakowska

openspec-continue-change

Create the next required artifact in an OpenSpec change workflow.

Community
Advanced
wtg42wtg42

openspec-continue-change

Create the next OpenSpec change artifact from CLI status and dependencies.

Community
Intermediate