openspec-continue-change

Name: openspec-continue-change
Availability: InStock
Author: cookeyholder

Create the next OpenSpec artifact in sequence using the CLI.

Updated Apr 9, 2026

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

Ready to run

npx skills add https://github.com/cookeyholder/django-devcontainer-template --skill openspec-continue-change-cookeyholder

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: openspec-continue-change
Source: https://github.com/cookeyholder/django-devcontainer-template/tree/main/.agent/skills/openspec-continue-change
Command: npx skills add https://github.com/cookeyholder/django-devcontainer-template --skill openspec-continue-change-cookeyholder

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams advance an OpenSpec change by generating the next required artifact in the sequence, ensuring a structured, traceable progression.

Core Features & Use Cases

Continue a change by creating the next artifact using the OpenSpec CLI.
Retrieve and assess change status, available changes, and dependencies to guide artifact creation.
Generate artifact files from a template, reading completed dependencies and applying workflow rules to maintain order and consistency.

Quick Start

Run the openspec continue-change command with a change name to generate the next artifact.

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, use the CLI to retrieve the change status and generate the next required artifact in the sequence. This enforces dependency checks and template-based creation to ensure artifacts are created in the proper order.

What is the OpenSpec workflow sequence for artifact creation?▼

The OpenSpec workflow sequence is a CLI-driven process that enforces dependency checks and status-oriented progression. It ensures artifacts are generated from templates in a structured order, maintaining traceability throughout the change lifecycle.

How do I ensure OpenSpec dependencies are checked before creating a new artifact?▼

OpenSpec dependency checks are enforced automatically when you continue a change. The workflow reads completed dependencies and applies rules to guide artifact creation, ensuring prerequisites are met before generating the next template-based file.

Can I use OpenSpec to update an ongoing change with new artifacts?▼

Yes, you can update an ongoing OpenSpec change by progressing through artifacts. The CLI assesses the current change status and available dependencies to generate the next required artifact, maintaining sequence and consistency.

What is the best way to manage OpenSpec artifact progression for a team?▼

The best way to manage OpenSpec artifact progression is using the CLI continue-change command. It retrieves change status, enforces dependency checks, and applies template-based creation to ensure structured, traceable progression for your team.

Why does OpenSpec enforce a specific sequence for creating change artifacts?▼

OpenSpec enforces a specific artifact creation sequence to maintain order and consistency. By applying status-oriented progression and dependency checks, the workflow ensures traceable and structured changes throughout the project lifecycle.