openspec-continue-change

Create the next OpenSpec workflow artifact from an existing change state.

1|Updated Apr 22, 2026
One-click install
npx skills add https://github.com/evandrodevbr/GeminiNexus --skill openspec-continue-change-evandrodevbr
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-continue-change
Source: https://github.com/evandrodevbr/GeminiNexus/tree/main/.claude/skills/openspec-continue-change
Command: npx skills add https://github.com/evandrodevbr/GeminiNexus --skill openspec-continue-change-evandrodevbr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps users continue OpenSpec-driven changes without losing workflow state, ensuring the next required artifact is created in the correct order.

Core Features & Use Cases

  • Workflow Progression: Checks OpenSpec change status and determines the next available artifact to create.
  • Artifact Generation Guidance: Retrieves artifact instructions, dependencies, and templates before creating the required deliverable.
  • Use Case: Continue a software change request by selecting an existing OpenSpec change and generating the next proposal, specification, design, or task artifact.

Quick Start

Use the openspec-continue-change skill to continue the current OpenSpec change workflow and create the next required 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 request workflow?

To continue an OpenSpec change request workflow, the skill checks the CLI status to determine the current state and retrieves instructions to create the next required artifact in the correct sequence.

What is spec driven change management for software engineering?

Spec driven change management structures software modifications through ordered artifact generation, ensuring dependencies are handled and deliverables like proposals, specifications, designs, and tasks are created sequentially.

How do I generate the next artifact for an existing OpenSpec change?

You generate the next artifact by retrieving templates and dependency instructions based on the existing change state, then creating the required deliverable to progress the software workflow.

Do I need the openspec CLI to automate artifact generation?

Yes, CLI automation requires the openspec CLI because the skill relies on its status checks and instruction retrieval to determine the next workflow artifact and manage dependencies correctly.

Why does my OpenSpec workflow lose state during software changes?

Workflow state is lost when artifact generation is not ordered correctly, but this skill prevents that by checking the OpenSpec change status and guiding the creation of the next required deliverable.