openspec-continue-change

Create the next artifact in an OpenSpec change workflow.

10|Updated Jan 28, 2026
One-click install
npx skills add https://github.com/AGIBuild/Agibuild.Fulora --skill openspec-continue-change-agibuild
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-continue-change
Source: https://github.com/AGIBuild/Agibuild.Fulora/tree/main/.cursor/skills/openspec-continue-change
Command: npx skills add https://github.com/AGIBuild/Agibuild.Fulora --skill openspec-continue-change-agibuild

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill helps you progress your development workflow by creating the next required artifact for an OpenSpec change, ensuring a structured and guided development process.

Core Features & Use Cases

  • Artifact Generation: Automatically creates the next artifact (e.g., proposal, spec, design, task) based on the current state of an OpenSpec change.
  • Workflow Guidance: Follows a defined schema to ensure artifacts are created in the correct order and with the necessary context.
  • Use Case: After defining a new capability in a proposal, use this Skill to automatically generate the corresponding specification file, moving your change closer to implementation.

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 generate the next artifact for an OpenSpec change?

To generate the next artifact for an OpenSpec change, you use a schema-driven workflow tool that automatically creates the required proposal, spec, design, or task file based on your current change status.

What is the spec-driven workflow schema for development change management?

The spec-driven workflow schema is a predefined sequence for change management that structures artifact generation into four distinct phases: proposal, specs, design, and tasks.

Do I need the openspec CLI to continue a change workflow?

Yes, you need the openspec CLI installed to continue a change workflow, as the system relies on it to retrieve status, list changes, and fetch the instructions needed for artifact generation.

How do I automatically create a specification file after defining a proposal?

You can automatically create a specification file after defining a proposal by running the continue change process, which reads your current workflow state and generates the subsequent spec artifact.

Can I ensure schema compliance when generating development artifacts?

Yes, you can ensure schema compliance during artifact generation because the workflow strictly follows a predefined schema to guarantee that all development artifacts are created in the correct order.