openspec-continue-change

Name: openspec-continue-change
Availability: InStock
Author: moltbook-experiments

Generates the next artifact for an ongoing OpenSpec change using the openspec CLI.

3|1|Updated Feb 1, 2026

Search Tags:#automation #workflow #cli #openspec #artifact #progress-tracking #change-management

Ready to run

npx skills add https://github.com/moltbook-experiments/glasshouse-protocol --skill openspec-continue-change-moltbook-experiments

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: openspec-continue-change
Source: https://github.com/moltbook-experiments/glasshouse-protocol/tree/main/.github/skills/openspec-continue-change
Command: npx skills add https://github.com/moltbook-experiments/glasshouse-protocol --skill openspec-continue-change-moltbook-experiments

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill automates continuing an OpenSpec change by generating the next artifact, enabling seamless progression through the change lifecycle.

Core Features & Use Cases

Artifact progression: Automatically determine and create the next artifact in the OpenSpec workflow (e.g., from proposal to specs to design to tasks).
Status-aware creation: Check current change status and generate artifacts in the correct order, respecting dependencies.
Guided workflow: Provide structured prompts and instructions to guide users through the next steps until completion.

Quick Start

Run openspec continue-change to generate the next artifact for your selected OpenSpec change and follow the prompts.

Frequently Asked Questions about openspec-continue-change

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

FAQPage Schema

How do I generate the next artifact for an ongoing OpenSpec change?▼

To generate the next OpenSpec artifact, run the openspec continue-change command. It inspects the current workflow status, reads dependency artifacts, and writes the next schema-defined artifact, enforcing one artifact per invocation.

How does OpenSpec workflow automation handle dependency-aware sequencing?▼

OpenSpec workflow automation handles dependency-aware sequencing by inspecting current change status and reading prior artifacts before creating the next one. This ensures artifacts generate in the correct order, respecting dependencies from proposal to tasks.

Can I automate OpenSpec change progression from proposal to tasks?▼

Yes, you can automate OpenSpec change progression from proposal to tasks by running continue-change. It applies to ongoing changes, handling progression and artifact creation sequentially until the tasks artifact is generated.

Do I need the openspec CLI to continue creating change artifacts?▼

Yes, you need the openspec CLI installed to continue creating change artifacts. The skill relies on the CLI to inspect current status, read dependency artifacts, and write the next schema-defined template while enforcing guardrails.

Why does my OpenSpec change only generate one artifact per invocation?▼

OpenSpec change workflows generate one artifact per invocation to enforce dependency-aware sequencing and guardrails. This prevents skipping required steps, ensuring each artifact properly builds upon the dependency artifacts read during status inspection.

What is the best way to resume an interrupted OpenSpec change workflow?▼

The best way to resume an interrupted OpenSpec change workflow is running openspec continue-change. It inspects current status and generates the next artifact using the schema-defined template, providing structured prompts to guide progression until completion.