openspec-continue-change

Generate the next artifact in an OpenSpec change workflow.

26|1|Updated May 2, 2022
One-click install
npx skills add https://github.com/anssip/passlane --skill openspec-continue-change-anssip
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-continue-change
Source: https://github.com/anssip/passlane/tree/main/.pi/skills/openspec-continue-change
Command: npx skills add https://github.com/anssip/passlane --skill openspec-continue-change-anssip

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automatically continues an OpenSpec change workflow by generating the next artifact, helping teams progress changes without stalling.

Core Features & Use Cases

  • Automates continuation of a change through its artifact sequence: list changes, select one, and create the required artifact file in the correct order.
  • Enforces dependency awareness by reading completed artifacts to inform new artifact creation.
  • Provides guardrails to ensure artifacts are created only when allowed by the schema, and outputs are written to the specified path.

Quick Start

Run openspec continue-change with a targeted 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 automate the next artifact generation in an OpenSpec change workflow?

Automating OpenSpec change workflows involves using a CLI command to list available changes, select one, and generate the required artifact file in the correct dependency-aware order to prevent workflow stalling.

What is dependency-aware artifact creation in change management?

Dependency-aware artifact creation enforces schema constraints by reading completed artifacts to inform new artifact generation, ensuring files are only created when allowed and written to the correct specified path.

Do I need the openspec CLI to continue a change through its artifact sequence?

Yes, continuing an OpenSpec change requires the openspec CLI to advance the workflow, select a targeted change name, and output the next artifact file according to the schema's context-based constraints.

How to step through an artifact sequence and generate the next required file?

To step through an artifact sequence, run the continue-change command with a targeted change name, which lists changes, picks one, and generates the required artifact file in the correct dependency order.

Why does my OpenSpec change workflow stall before creating the next artifact?

An OpenSpec change workflow stalls when dependency-aware constraints are not met, requiring the continue-change automation to read completed artifacts and enforce the correct order before creating the next file.