openspec-continue-change

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

39|6|Updated Apr 22, 2025

Search Tags:#automation #workflow #cli #openspec #artifact #change-management #engineering-process

Ready to run

npx skills add https://github.com/danielsogl/copilot-workflow-demo --skill openspec-continue-change-danielsogl

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: openspec-continue-change
Source: https://github.com/danielsogl/copilot-workflow-demo/tree/main/.github/skills/openspec-continue-change
Command: npx skills add https://github.com/danielsogl/copilot-workflow-demo --skill openspec-continue-change-danielsogl

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Continue working on an OpenSpec change by creating the next artifact to progress a workflow without losing context.

Core Features & Use Cases

Determine change status, identify the next required artifact using openspec list/status and select the next artifact to create.
Read completed dependencies and apply artifact templates to generate the new artifact, ensuring alignment with the current schema and rules.
Guardrails enforce correct sequencing, dependency awareness, and validation before writing to disk.

Quick Start

Continue the OpenSpec workflow by creating the next artifact for the current 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 continue an OpenSpec change and generate the next artifact?▼

To continue an OpenSpec change, the workflow reads the current change status via the OpenSpec CLI, resolves the next ready artifact, and writes it to disk using the appropriate template. This ensures progression across the workflow without losing context.

What is artifact sequencing in OpenSpec change management?▼

Artifact sequencing in OpenSpec change management enforces correct ordering by reading completed dependencies and applying templates. Guardrails validate dependency awareness before writing the new artifact, ensuring alignment with the current schema and rules.

Do I need the OpenSpec CLI to automate workflow artifact creation?▼

Yes, you need the OpenSpec CLI to automate workflow artifact creation. The process requires the CLI to list change status, identify the next required artifact, and apply the necessary template to write the new artifact to disk.

How does dependency awareness work when creating OpenSpec artifacts?▼

Dependency awareness works by reading completed dependencies before generating the next artifact. This ensures the new artifact aligns with the current schema and rules, with guardrails validating that all required dependencies are met before writing to disk.

What are the limitations of automating OpenSpec change progression?▼

The limitation of automating OpenSpec change progression is that it enforces strict sequencing and validation guardrails. If dependencies are not ready or the schema is not met, the workflow will not write the artifact, preventing out-of-order generation.