openspec-continue-change

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

Continue OpenSpec workflows by creating the next artifact in sequence.

Updated Feb 15, 2026

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

Ready to run

npx skills add https://github.com/mazhewitt/budget-analyser --skill openspec-continue-change-mazhewitt

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: openspec-continue-change
Source: https://github.com/mazhewitt/budget-analyser/tree/main/.gemini/skills/openspec-continue-change
Command: npx skills add https://github.com/mazhewitt/budget-analyser --skill openspec-continue-change-mazhewitt

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Continue working on a change by creating the next artifact.

Core Features & Use Cases

Guided continuation: checks status via the OpenSpec CLI, identifies the next eligible artifact, and fetches its instructions.
Dependency-aware artifact creation: reads completed artifacts before creating a new one to preserve context.
Enforces correct sequencing: prevents skipping artifacts and ensures artifacts unlock in the proper order.

Quick Start

Ask me to continue the current change and 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 workflow and generate the next artifact?▼

To continue an OpenSpec workflow, the skill checks current artifact status via the CLI, identifies the next eligible artifact, and fetches its instructions to guide creation. It reads completed dependency artifacts first to preserve context and ensure correct sequencing.

How does dependency-aware artifact creation work in specification workflows?▼

Dependency-aware artifact creation works by reading completed artifacts before generating a new one. This preserves context and ensures the new artifact adheres to schema-driven generation rules, retrieving necessary instructions and dependencies before writing to the designated path.

Can I skip artifact steps when managing OpenSpec changes?▼

You cannot skip artifact steps. The skill enforces correct sequencing by applying order constraints, preventing skipping artifacts, and ensuring each artifact unlocks in the proper order based on dependency status retrieved from the CLI.

Do I need the OpenSpec CLI to automate change continuation?▼

You need the OpenSpec CLI to automate change continuation. The skill uses the CLI to check the current artifact status, retrieve artifact instructions, and determine the next eligible artifact before writing the new artifact to the designated path.

What is the best way to manage artifact sequencing for automated specification changes?▼

The best way to manage artifact sequencing is using a schema-driven approach that reads dependency artifacts before creation. This prevents skipping steps, enforces correct unlocking order, and writes new artifacts to designated paths based on CLI status checks.

Why does my workflow artifact creation fail when dependencies are not read?▼

Workflow artifact creation fails because the skill requires reading completed dependency artifacts before creating a new one. This dependency-aware mechanism preserves context and enforces correct sequencing to avoid skipping steps in the OpenSpec workflow.