openspec-continue-change

Create the next OpenSpec artifact in a change workflow.

1|Updated Jul 30, 2023

Search Tags:#workflow automation #specification #development process #change management #openspec #artifact generation

Ready to run

npx skills add https://github.com/DanielShuguang/tool-box --skill openspec-continue-change-danielshuguang

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: openspec-continue-change
Source: https://github.com/DanielShuguang/tool-box/tree/main/.trae/skills/openspec-continue-change
Command: npx skills add https://github.com/DanielShuguang/tool-box --skill openspec-continue-change-danielshuguang

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires openspec-cn, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps users continue their work on OpenSpec changes by creating the next artifact in a workflow, ensuring progress and completion of defined specifications.

Core Features & Use Cases

Progressive Artifact Creation: Automatically generates the next required artifact (e.g., proposal, spec, design, tasks) based on the current state of an OpenSpec change.
Workflow Management: Guides users through the OpenSpec change lifecycle, ensuring artifacts are created in the correct order and with necessary context.
Use Case: After a user has created a 'proposal.md' for a new feature, they can use this Skill to automatically generate the corresponding 'spec.md' files for each capability defined in the proposal.

Quick Start

Use the openspec-continue-change skill to create the next artifact for the 'add-user-auth' 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 automate specification creation for the next step in a software development change?▼

Automating specification creation is handled by generating the next required artifact in the OpenSpec workflow, such as automatically creating a spec.md file after a proposal.md is defined. This ensures progressive artifact creation in the correct order.

What is the best way to continue an OpenSpec change workflow after creating a proposal?▼

The best way to continue an OpenSpec change workflow is by generating the next artifact based on the current change state. After creating a proposal, this process automatically guides users to generate corresponding spec.md files for each defined capability.

Do I need the openspec CLI to manage specification and design artifacts?▼

Yes, you need the openspec CLI to manage specification and design artifacts. The continuation process requires the CLI to list changes, check status, and generate instructions for the next artifact in the software development lifecycle.

How does artifact generation manage the lifecycle of specifications, designs, and tasks?▼

Artifact generation manages the lifecycle of specifications, designs, and tasks by creating the next required document based on the current workflow state. This ensures artifacts are generated sequentially with the necessary context for software development changes.

Can I use workflow automation to generate multiple spec files from one proposal?▼

Yes, you can use workflow automation to generate multiple spec files from one proposal. When continuing an OpenSpec change, the process automatically generates corresponding spec.md files for each capability defined in the initial proposal.md document.