skills.rest
carlosapgomes
carlosapgomesCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

openspec-continue-change

Continue an OpenSpec change by creating the next workflow artifact.

Updated May 29, 2025
Search Tags:#workflow#cli#spec#openspec#artifact#change-management
One-click install
npx skills add https://github.com/carlosapgomes/eqmd --skill openspec-continue-change-carlosapgomes
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-continue-change
Source: https://github.com/carlosapgomes/eqmd/tree/main/.claude/skills/openspec-continue-change
Command: npx skills add https://github.com/carlosapgomes/eqmd --skill openspec-continue-change-carlosapgomes

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill continues an OpenSpec change by creating the next artifact to progress the workflow, guiding you through selection and artifact creation.

Core Features & Use Cases

  • Orchestrates the next artifact in the OpenSpec lifecycle (proposal → specs → design → tasks) based on the current status.
  • Handles dependency reading, template application, and safe writing of artifacts to the repository.
  • Supports status checks, user prompts for unclear changes, and enforcement of sequencing.

Quick Start

Ask to generate the next artifact for the selected change to progress the OpenSpec workflow.

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 to generate the next artifact in the workflow?▼

The OpenSpec change workflow follows a strict sequencing lifecycle from proposal to specs, then design, and finally tasks. The Skill enforces this sequence by checking the current change status and only allowing the creation of the next valid artifact in the progression.

How does artifact sequencing work when progressing an OpenSpec change?▼

The OpenSpec change workflow follows a strict sequencing lifecycle from proposal to specs, then design, and finally tasks. The Skill enforces this sequence by checking the current change status and only allowing the creation of the next valid artifact in the progression.

What do I need to provide to create the next spec artifact for an OpenSpec change?▼

You need to provide the change name if it is not already clear from the context. The Skill then operates within the OpenSpec CLI to resolve dependencies, apply the artifact template, and perform safety checks before writing the new artifact file.

Can I skip the design phase and jump straight to tasks in an OpenSpec change workflow?▼

No, you cannot skip phases. The Skill enforces strict artifact sequencing and performs safety checks before creation, ensuring that dependencies for the next artifact are fully resolved and the previous steps in the change lifecycle are completed.

Why does my OpenSpec change workflow stop before writing the new artifact file?▼

The workflow halts if safety checks fail, dependencies are unresolved, or the change name is missing. The Skill enforces template usage and sequencing rules, prompting you to provide the required change name or resolve issues before safely writing the artifact.

Related Skills

Explore More Software Engineering Skills→
danielsogldanielsogl
39

openspec-continue-change

Generate the next OpenSpec workflow artifact using the CLI and templates.

Community
Advanced
SAPSAP
221

openspec-continue-change

Create the next OpenSpec artifact using the OpenSpec CLI.

Official
Advanced
Max-LooMax-Loo
2

openspec-continue-change

Create the next OpenSpec change artifact after checking status and dependencies.

Community
Advanced
finger-gunfinger-gun
4

openspec-ff-change

Scaffold OpenSpec change artifacts with dependency-aware sequencing and guided prompts.

Official
Advanced