openspec-continue-change

Generate the next OpenSpec artifact in a schema-driven workflow sequence.

1|Updated Feb 6, 2026
One-click install
npx skills add https://github.com/emergent-company/emergent.memory --skill openspec-continue-change-emergent-company
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-continue-change
Source: https://github.com/emergent-company/emergent.memory/tree/main/.opencode/skills/openspec-continue-change
Command: npx skills add https://github.com/emergent-company/emergent.memory --skill openspec-continue-change-emergent-company

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires openspec, and includes scripts (resource) components.

What problem does it solve?

This Skill streamlines the development workflow for OpenSpec changes by automating the creation of subsequent artifacts, ensuring progress and adherence to defined schemas.

Core Features & Use Cases

  • Progressive Artifact Creation: Automatically generates the next required artifact (e.g., proposal, spec, design, tasks) based on the current status of an OpenSpec change.
  • Schema-Driven Workflow: Adapts to different workflow schemas (e.g., "spec-driven") to create artifacts in the correct sequence.
  • Use Case: After creating a proposal for a new feature, use this Skill to automatically generate the corresponding specification file, then the design document, and finally the implementation tasks, guiding you through the entire change lifecycle.

Quick Start

Use the openspec-continue-change skill to create the next artifact for the 'user-authentication' 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 for an OpenSpec change?

You can automatically generate the next OpenSpec artifact by running this Skill, which checks the current change status and creates the subsequent proposal, specification, design, or task file required by your predefined schema.

What is a schema-driven workflow for software development changes?

A schema-driven workflow is a structured development process that adapts to predefined schemas, such as spec-driven, to generate artifacts in a specific sequence like proposals, specifications, designs, and implementation tasks.

Do I need the openspec CLI to advance a change through its workflow?

Yes, you need the openspec CLI installed to advance a change, as this Skill relies on it for retrieving instructions, checking artifact status, and generating the required workflow files.

How do I create specifications and design documents after a proposal?

To create specifications and design documents after a proposal, you use a continuous workflow Skill that identifies the completed proposal and automatically generates the next required specification and design artifacts.

What is the best way to manage implementation tasks in a spec-driven workflow?

The best way to manage implementation tasks in a spec-driven workflow is to automate their generation based on artifact dependencies, ensuring tasks are created only after specifications and designs are finalized.

Why does my OpenSpec artifact generation stop before creating tasks?

Your OpenSpec artifact generation stops because the workflow sequence depends on artifact status; if prerequisite specifications or designs are missing or incomplete, the system prevents creating subsequent implementation tasks.