openspec-continue-change

Automates OpenSpec change progression by creating the next artifact via CLI commands.

Updated Jan 23, 2026
One-click install
npx skills add https://github.com/lz-freedom/polybull-stock-helper --skill openspec-continue-change-lz-freedom
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-continue-change
Source: https://github.com/lz-freedom/polybull-stock-helper/tree/main/.opencode/skills/openspec-continue-change
Command: npx skills add https://github.com/lz-freedom/polybull-stock-helper --skill openspec-continue-change-lz-freedom

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Continue working on an OpenSpec change by creating the next artifact, enabling teams to progress a workflow without rebuilding from scratch.

Core Features & Use Cases

  • Automatic progression: determine the current change, identify the next required artifact, and generate it automatically.
  • Dependency-aware execution: reads completed artifacts to ensure proper sequencing and avoids skipping steps.
  • CLI-driven workflow: uses the openspec commands (status, instructions) to guide artifact creation within an existing toolchain.

Quick Start

Use openspec to list changes, check status for a change, and fetch the next artifact instructions:

  • Open a change: openspec list --json
  • Inspect progress: openspec status --change "<name>" --json
  • Get instructions: openspec instructions <artifact-id> --change "<name>" --json
  • Generate the artifact following the provided template and place it in the path indicated by the instructions.

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, you automate progression by running `openspec status` to inspect the current workflow, retrieve the next artifact instructions via `openspec instructions`, and write the generated artifact to the specified output path while honoring dependency order.

What is the process for automating OpenSpec change management via CLI?

Automating OpenSpec change management involves using CLI commands to read a change's current status, fetch templated instructions for the next required artifact, and generate the file automatically to progress the workflow without rebuilding from scratch.

How does dependency-aware execution work when creating OpenSpec artifacts?

Dependency-aware execution works by reading completed artifacts to ensure proper sequencing within the OpenSpec workflow, preventing the automation from skipping required steps or generating artifacts out of order.

Do I need to manually track workflow steps to create the next OpenSpec artifact?

No, you do not need to manually track workflow steps. The automation determines the current change, identifies the next required artifact by reading completed steps, and generates it automatically using CLI instructions and templated structures.

Why does my OpenSpec workflow skip dependency order when generating artifacts?

OpenSpec workflows skip dependency order when the automation fails to read completed artifacts properly. To resolve this, ensure the CLI reads the current status correctly before fetching instructions and writing the next artifact to the output path.