openspec-continue-change

Continue an OpenSpec change by generating the next schema-ordered artifact.

1|1|Updated May 5, 2026
One-click install
npx skills add https://github.com/cynkra/cynkra.ai.day --skill openspec-continue-change-cynkra
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-continue-change
Source: https://github.com/cynkra/cynkra.ai.day/tree/main/indietypst/.claude/skills/openspec-continue-change
Command: npx skills add https://github.com/cynkra/cynkra.ai.day --skill openspec-continue-change-cynkra

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you reliably continue an OpenSpec change without losing the correct artifact order, dependencies, or schema workflow state.

Core Features & Use Cases

  • Resume next artifact: Continues the change by selecting the next artifact that is marked ready and generating only that one artifact per run.
  • Schema-aware workflow: Uses the current OpenSpec status and artifact instructions to follow the correct schema-specific sequence.
  • Dependency-first context: Reads completed dependency artifacts before writing the next artifact to maintain consistency.
  • User-guided change selection: Prompts you to choose among recently modified changes when a change name is not provided.

Quick Start

Ask the AI to continue an OpenSpec change by saying: Continue the most recent OpenSpec change and create 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 after an interruption?

To continue an OpenSpec change, the workflow selects the next ready artifact and generates it in the correct schema-defined order. It reads completed dependency artifacts first to maintain consistency before writing the output.

What is spec-driven development artifact generation workflow?

Spec-driven development artifact generation is a schema-aware process that creates exactly one artifact per run in a correct sequence. It fetches artifact instructions, reads dependencies, and writes the next spec, design, or task output.

How do I generate the next spec, design, or task artifact for an in-progress change?

Generate the next artifact by running a workflow continuation that identifies the next ready item in the schema sequence. The process fetches instructions, reads completed dependencies for context, and writes the artifact to the outputPath.

Does OpenSpec workflow continuation maintain dependency order between artifacts?

Yes, OpenSpec workflow continuation maintains dependency order by reading completed dependency artifacts before writing the next output. This dependency-first context ensures consistency across the schema-defined sequence during generation.

Do I need the OpenSpec CLI to automate artifact generation for changes?

Yes, the OpenSpec CLI is required to automate artifact generation as it lists changes, checks status, and fetches schema instructions. The workflow uses these CLI outputs to determine the sequence and write the artifact.

Can I choose which OpenSpec change to resume if multiple are in progress?

Yes, you can choose which OpenSpec change to resume when a specific change name is not provided. The workflow prompts you to select among recently modified changes before generating the next artifact.