skills.rest
CloudDevCrusader
CloudDevCrusaderCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

openspec-continue-change

Generate the next OpenSpec workflow artifact from change status.

1|Updated Jan 11, 2026
Search Tags:#development workflow#cli#schema-driven#change management#openspec#artifact generation
One-click install
npx skills add https://github.com/CloudDevCrusader/riddle-rush-mono-repo --skill openspec-continue-change-clouddevcrusader
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-continue-change
Source: https://github.com/CloudDevCrusader/riddle-rush-mono-repo/tree/main/.claude/skills/openspec-continue-change
Command: npx skills add https://github.com/CloudDevCrusader/riddle-rush-mono-repo --skill openspec-continue-change-clouddevcrusader

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you continue working on your OpenSpec changes by automating the creation of the next required artifact in your development workflow.

Core Features & Use Cases

  • Automated Artifact Generation: Creates the next artifact based on the current status of an OpenSpec change.
  • Workflow Progression: Guides you through the OpenSpec development lifecycle, ensuring artifacts are created in the correct order.
  • Use Case: After creating a proposal for a new feature, you can use this Skill to automatically generate the corresponding specification file.

Quick Start

Use the openspec-continue-change skill to create the next artifact for your change.

Frequently Asked Questions about openspec-continue-change

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

FAQPage Schema
How do I create the next artifact in my schema-driven development workflow?▼

To create the next artifact in schema-driven development, this Skill checks your current OpenSpec change status and automatically generates the required proposal, specification, design, or task file for your workflow.

What is the OpenSpec change progression process for generating specifications?▼

The OpenSpec change progression process uses the openspec CLI to retrieve artifact instructions and generate specifications, designs, and tasks sequentially, ensuring your development lifecycle artifacts are created in the correct workflow order.

Do I need the openspec CLI to generate change proposals and tasks?▼

Yes, you need the openspec CLI installed because this Skill relies on it to perform status checks and retrieve artifact instructions required to generate proposals, specifications, designs, and tasks for your changes.

Can I automatically generate a specification file after creating a proposal?▼

Yes, you can automatically generate a specification file after creating a proposal. The Skill evaluates your current OpenSpec change status and produces the corresponding next artifact to progress your defined workflow.

What's the best way to manage change artifacts in schema-driven development?▼

The best way to manage change artifacts in schema-driven development is automating workflow progression, which ensures your proposals, specifications, designs, and tasks are generated sequentially based on your OpenSpec change status.

Related Skills

Explore More Software Engineering Skills→
ywh0606ywh0606

opsx-new-change

Create OpenSpec change directories and retrieve artifact instructions via the openspec CLI.

Community
Intermediate
dmitriybdmitriyb
4

review

Review GitHub pull requests against specifications and required tests.

Community
Advanced
tuliopc23tuliopc23

openspec-apply-change

Implement OpenSpec change tasks and update workflow progress.

Community
Advanced
jaxxstormjaxxstorm
4

openspec-continue-change

Create the next OpenSpec change artifact via the openspec CLI.

Community
Advanced