skills.rest
artagon
artagonOFFICIAL
Explore all skills by this author →
WebsiteGitHub

openspec-continue-change

Create the next required OpenSpec artifact from current workflow state.

Updated Nov 12, 2025
Search Tags:#CLI automation#spec-driven development#openspec#artifact generation#template rendering#dependency handling#workflow continuation
One-click install
npx skills add https://github.com/artagon/artagon-vscode-profiles --skill openspec-continue-change-artagon
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-continue-change
Source: https://github.com/artagon/artagon-vscode-profiles/tree/main/agents/skills/openspec-continue-change
Command: npx skills add https://github.com/artagon/artagon-vscode-profiles --skill openspec-continue-change-artagon

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It solves the problem of getting stuck mid-work on an OpenSpec change by guiding you to create the next required artifact in the correct order.

Core Features & Use Cases

  • Resumes from actual workflow state: Inspects the change’s current artifact statuses so you continue where you left off.
  • Interactive change selection: When the change name is missing, prompts you to choose from the most recently modified options without guessing.
  • Next-artifact creation with dependencies: Reads dependency artifacts for context, uses the provided template, and writes exactly one new output artifact.
  • Completion-aware behavior: Stops and confirms when the change is complete, otherwise reports what is newly unlocked.

Quick Start

Ask the AI to continue an OpenSpec change by running openspec-continue-change and optionally providing the change name if you already know it.

Frequently Asked Questions about openspec-continue-change

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I resume an OpenSpec change and generate the next artifact in sequence?▼

To resume an OpenSpec change, the workflow inspects current artifact statuses and creates the next required file in sequence. It reads dependency outputs, renders the provided template, and writes exactly one new artifact to continue the workflow safely.

How does spec-driven development handle artifact dependencies when continuing a workflow?▼

Spec-driven workflow continuation handles dependencies by reading completed dependency files for context, selecting the first ready artifact, and rendering its template to generate the required output sequentially.

Do I need the openspec CLI to automate template rendering for spec-driven changes?▼

Yes, you need the openspec CLI to automate template rendering. The CLI lists changes, queries artifact status and instructions in JSON, and writes the rendered template to the correct output path.

What happens when an OpenSpec change is complete during workflow continuation?▼

When an OpenSpec change is complete, the workflow continuation stops and confirms the completion. If artifacts remain, it reports what is newly unlocked and selects the next ready artifact for generation.

How do I select an OpenSpec change to continue if I don't know the exact name?▼

If the change name is missing, the workflow prompts you to interactively select an OpenSpec change to continue. It displays the most recently modified options for selection without guessing.

Related Skills

Explore More Software Engineering Skills→
SAPSAP
221

openspec-continue-change

Create the next OpenSpec artifact using the OpenSpec CLI.

Official
Advanced
em-jonesem-jones
1

Implement Pre-Commit Hooks Integration

Render OpenSpec artifact files from td state before each git commit.

Community
Advanced
arestivoarestivo

openspec-continue-change

Generate the next OpenSpec change artifact from CLI status and instructions.

Community
Advanced
igamenovoerigamenovoer
18

openspec-continue-change

Continues an OpenSpec workflow by generating the next required artifact for a selected change.

Community
Intermediate