openspec-continue-change

Generate the next required OpenSpec artifact from current change status.

1|Updated Feb 11, 2026
One-click install
npx skills add https://github.com/vidos-id/usecase-demos --skill openspec-continue-change-vidos-id
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-continue-change
Source: https://github.com/vidos-id/usecase-demos/tree/main/.agents/skills/openspec-continue-change
Command: npx skills add https://github.com/vidos-id/usecase-demos --skill openspec-continue-change-vidos-id

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill helps you continue working on your OpenSpec changes by guiding you through the creation of the next required artifact in your workflow.

Core Features & Use Cases

  • Artifact Generation: Creates the next artifact based on the current status of an OpenSpec change.
  • Workflow Progression: Ensures you follow the defined steps for developing a change, from proposal to implementation.
  • Use Case: After creating a proposal for a new feature, you can use this Skill to automatically generate the corresponding specification file, ensuring you stay on track with development.

Quick Start

Use the openspec-continue-change skill to continue working on your current 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 continue an OpenSpec change workflow and generate the next artifact?

You can continue OpenSpec development by using this Skill to check your current change status and generate the next required artifact, ensuring proper workflow progression from proposal to implementation.

What schemas does the OpenSpec artifact generation process support?

The artifact generation process supports the 'spec-driven' schema, which includes creating proposal, specs, design, and tasks artifacts to guide your development workflow.

Do I need the OpenSpec CLI installed to progress my development changes?

Yes, the OpenSpec CLI is required to progress your development changes, as this Skill relies on it for performing status checks and retrieving artifact instructions.

How do I automatically generate a specification file after creating a proposal?

You can automatically generate a specification file after creating a proposal by using this Skill to evaluate your current change status and produce the corresponding next artifact in the spec-driven workflow.

What is the best way to ensure I follow defined steps when developing an OpenSpec change?

The best way to ensure you follow defined steps when developing an OpenSpec change is to use this Skill to generate each subsequent artifact sequentially, from proposal to implementation, based on status checks.