openspec-continue-change

Create the next OpenSpec workflow artifact after checking progress and dependencies.

4|2|Updated Aug 27, 2025
One-click install
npx skills add https://github.com/finger-gun/sisu --skill openspec-continue-change-finger-gun
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-continue-change
Source: https://github.com/finger-gun/sisu/tree/main/.kilocode/skills/openspec-continue-change
Command: npx skills add https://github.com/finger-gun/sisu --skill openspec-continue-change-finger-gun

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Continue working on an OpenSpec change by creating the next artifact.

Core Features & Use Cases

  • Artifact orchestration: guide the user to identify and create the next artifact in the OpenSpec workflow.
  • Status-aware creation: check current progress and trigger artifact generation when the next artifact is ready.
  • Dependency-aware: read completed artifacts to satisfy prerequisites before writing the new artifact.

Quick Start

Continue the OpenSpec change by creating 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 create the next artifact?

To continue an OpenSpec change, the workflow checks current progress, resolves dependencies from completed artifacts, selects the next artifact, and writes it according to the schema.

What is artifact orchestration in OpenSpec workflow management?

Artifact orchestration in OpenSpec workflow management guides users to identify and create the next artifact by reading status, resolving dependencies, and triggering artifact generation when ready.

Do I need the OpenSpec CLI to generate workflow artifacts?

Yes, you need the OpenSpec CLI to generate workflow artifacts. The CLI reads the change status, resolves dependencies, and writes artifacts according to the required schema.

How does status-aware artifact creation work in OpenSpec?

Status-aware artifact creation checks current progress within the OpenSpec workflow and triggers artifact generation only when the next artifact is ready and dependencies are resolved.

What's the best way to manage dependencies when creating OpenSpec artifacts?

To manage dependencies when creating OpenSpec artifacts, the workflow reads completed artifacts to satisfy prerequisites before writing the new artifact, ensuring schema compliance.