openspec-continue-change

Create the next OpenSpec artifact in the workflow sequence.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill helps users systematically advance their OpenSpec changes by creating the necessary artifacts in the correct order, preventing workflow stagnation.

Core Features & Use Cases

  • Sequential Artifact Creation: Generates the next required artifact (proposal, specs, design, tasks) based on the current change status.
  • Contextual Guidance: Utilizes project context and rules to inform artifact content.
  • User-Guided Selection: Prompts the user to select a change if multiple are active or ambiguous.
  • Use Case: After creating a proposal for a new feature, use this skill to automatically generate the corresponding specification documents.

Quick Start

Use the openspec continue change skill to create the next artifact for the 'add-user-profile' 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 automatically generate the next artifact in an OpenSpec change workflow?

To generate the next artifact in an OpenSpec change workflow, use this skill to sequentially create proposals, specs, designs, or tasks based on your current change status and schema.

What is the process for advancing spec-driven development changes step-by-step?

Advancing spec-driven development changes involves creating required artifacts sequentially, preventing workflow stagnation by generating the next document based on current project context and rules.

Do I need the OpenSpec CLI to generate change artifacts like proposals and tasks?

Yes, you need the OpenSpec CLI installed and active changes with pending artifacts to generate the next required proposal, spec, design, or task document in the workflow sequence.

Can I use this workflow to generate specifications after creating a feature proposal?

Yes, after creating a feature proposal, you can use this skill to automatically advance the change by generating the corresponding specification documents and subsequent artifacts.

How do I handle artifact generation when multiple OpenSpec changes are active?

When multiple OpenSpec changes are active or ambiguous, the skill prompts you to select a specific change before generating the next required artifact for that particular workflow.

What are the limitations of automating change management artifact generation?

Limitations of automating change management artifact generation include requiring active changes with pending artifacts and relying entirely on the OpenSpec CLI environment to function correctly.