skills.rest
rangechow
rangechowCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

openspec-continue-change

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

Updated Apr 26, 2026
Search Tags:#automation#workflow#cli#artifacts#openspec#artifact-creation#change-management
One-click install
npx skills add https://github.com/rangechow/LotGameClient --skill openspec-continue-change-rangechow
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-continue-change
Source: https://github.com/rangechow/LotGameClient/tree/main/.claude/skills/openspec-continue-change
Command: npx skills add https://github.com/rangechow/LotGameClient --skill openspec-continue-change-rangechow

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the continuation of OpenSpec changes by generating the next artifact, reducing manual coordination and errors.

Core Features & Use Cases

  • Continue an in-progress OpenSpec change by creating the next artifact (e.g., proposal, specs, design, tasks) aligned with the current workflow.
  • Identify the target change, inspect its status, and generate artifacts in the correct sequence according to the active schema.
  • Automatically respect dependencies from completed artifacts and write outputs to the designated locations.

Quick Start

Select the target change and generate the next artifact to advance 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 automate OpenSpec change management to generate the next workflow artifact?▼

Automate OpenSpec change management by selecting a target change, verifying its status via the CLI, and generating the next artifact in sequence according to the active schema.

What is the process to continue an OpenSpec change that has pending artifacts?▼

Continuing an OpenSpec change involves identifying the target change, checking its pending status, and creating the next artifact while automatically respecting dependencies from completed artifacts.

How do I ensure generated artifacts respect dependencies in an OpenSpec workflow?▼

Generated artifacts respect dependencies by following the active schema, fetching artifact instructions, and writing outputs to designated paths only after completed artifact dependencies are honored.

Can I use the OpenSpec CLI to check change statuses and fetch artifact instructions?▼

Yes, you can use the OpenSpec CLI to list changes, check their statuses, fetch artifact instructions, and write the resulting artifact to its designated path to advance the workflow.

What's the best way to reduce manual coordination errors when creating OpenSpec artifacts?▼

Reduce manual coordination errors by proactively generating the next artifact in the correct sequence, ensuring the output aligns with the active schema and is written to the correct location.

When should I not use automated artifact creation for OpenSpec changes?▼

Avoid automated artifact creation for OpenSpec changes that do not have pending artifacts, as the workflow relies on identifying changes with pending statuses to generate the next artifact.

Related Skills

Explore More Software Engineering Skills→
runtime-envruntime-env
47

openspec-continue-change

Generate the next OpenSpec change artifact using the OpenSpec CLI.

Official
Advanced
danielsogldanielsogl
39

openspec-new-change

Scaffold OpenSpec changes with schema-aware artifact workflow instructions.

Community
Advanced
tungnguyen10tungnguyen10

openspec-continue-change

Identify and generate the next schema-compliant artifact in OpenSpec change workflows.

Community
Intermediate
goerngoern
113

openspec-new-change

Scaffold OpenSpec change directories and track artifact readiness.

Community
Advanced