openspec-continue-change

Create the next OpenSpec artifact for an in-progress change using the openspec CLI.

Updated Feb 25, 2026
One-click install
npx skills add https://github.com/futuretea/x-project --skill openspec-continue-change-futuretea
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-continue-change
Source: https://github.com/futuretea/x-project/tree/main/.claude/skills/openspec-continue-change
Command: npx skills add https://github.com/futuretea/x-project --skill openspec-continue-change-futuretea

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Continue working on an OpenSpec change by creating the next artifact, enabling seamless progression through a multi-artifact workflow.

Core Features & Use Cases

  • Orchestrates the continuation flow by selecting the target change, checking current artifact status, and determining the next actionable artifact to create.
  • Reads OpenSpec status and instructions via the openspec CLI to ensure correct sequencing and dependencies are respected.
  • Generates the next artifact file according to the schema's guidance, while respecting contextual constraints.

Quick Start

Ask me to continue the current OpenSpec change.

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 automation inspects the current artifact status via the openspec CLI, determines the next actionable artifact, fetches its specific instructions, and writes the new artifact file according to the template.

What is the best way to automate progression through a multi-artifact workflow?

Automating a multi-artifact workflow involves using the openspec CLI to check artifact sequencing and dependencies, then generating the next artifact file based on schema guidance to ensure seamless workflow progression and continuity.

How does the openspec CLI determine the next artifact for a change?

The openspec CLI inspects the current change status to determine the next actionable artifact, fetches the corresponding artifact instructions, and respects contextual constraints to write the correct file.

Do I need any specific dependencies to generate OpenSpec artifacts?

Generating OpenSpec artifacts requires no external dependencies, as the workflow relies entirely on the openspec CLI to read status, fetch instructions, and write the new artifact file according to the template.

Can I maintain workflow continuity if I skip creating an artifact in OpenSpec?

Maintaining workflow continuity requires creating artifacts in the correct sequence, as the automation uses the openspec CLI to check current status and ensure dependencies are respected before writing the next artifact file.

Why does my OpenSpec change workflow fail to fetch artifact instructions?

Fetching artifact instructions fails when the openspec CLI cannot inspect the current status or determine the next actionable artifact, preventing the automation from respecting dependencies and writing the new artifact file.