openspec-continue-change

Creates the next artifact in an OpenSpec change workflow using the openspec CLI.

Updated Jun 25, 2026
One-click install
npx skills add https://github.com/ismaelsoilet/ismaelsoilet-landing --skill openspec-continue-change-ismaelsoilet
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-continue-change
Source: https://github.com/ismaelsoilet/ismaelsoilet-landing/tree/main/.cursor/skills/openspec-continue-change
Command: npx skills add https://github.com/ismaelsoilet/ismaelsoilet-landing --skill openspec-continue-change-ismaelsoilet

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When working through a multi-artifact OpenSpec change (proposals, specs, tasks), it is easy to lose track of which artifact comes next and what structure it must follow. This Skill inspects the current change status and creates exactly the next ready artifact in the correct schema-defined order. ## Core Features & Use Cases - Status-Driven Progression: Runs openspec status to parse artifact states (done, ready, blocked) and picks the first artifact ready to create. - Schema-Aware Artifact Creation: Fetches per-artifact instructions, templates, and dependency files via openspec instructions, then writes the artifact to the resolved output path. - Ambiguity Handling: Lists recent changes and prompts the user to select one when the target change is unclear, marking the most recently modified as recommended. - Use Case: You have an OpenSpec change with a completed proposal and want the tasks file generated. Invoke this Skill and it reads the proposal from disk, applies the schema template, and writes tasks.md in the right location. ## Quick Start Ask the assistant to continue your OpenSpec change, optionally naming the change, and it will create the next pending artifact for you.

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 after creating the proposal?▼

Invoke the continue workflow with the change name, and it runs openspec status to find the first artifact marked ready. It then fetches the artifact's instructions and template, reads completed dependencies from disk, and writes the next file.

How does the skill decide which artifact to create next?▼

It parses the JSON output of openspec status, which lists artifacts with statuses like done, ready, or blocked. The first artifact with status ready is selected, following the schema's defined sequence rather than assumed file names.

What happens if I don't specify a change name?▼

The skill infers the change from conversation context or auto-selects when only one active change exists. If ambiguous, it runs openspec list --json and prompts you with the most recently modified changes, marking the newest as recommended.

Does this skill require the openspec CLI to be installed?▼

Yes, the skill depends entirely on the openspec CLI for status, instructions, list, and store commands. Without the CLI installed and an OpenSpec change present, the workflow cannot proceed.

Can it create multiple artifacts in one run?▼

No, the guardrails explicitly limit each invocation to creating exactly one artifact. After writing, it shows progress and what was unlocked, then stops so you can review before continuing.