openspec-continue-change

Generates the next OpenSpec workflow artifact from a schema-driven template.

9|16|Updated Oct 16, 2018
One-click install
npx skills add https://github.com/ondata/albopopTwoDotZero --skill openspec-continue-change-ondata
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-continue-change
Source: https://github.com/ondata/albopopTwoDotZero/tree/main/.gemini/skills/openspec-continue-change
Command: npx skills add https://github.com/ondata/albopopTwoDotZero --skill openspec-continue-change-ondata

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill automates the continuation of an OpenSpec change by guiding the user to create the next artifact in the workflow, reducing manual coordination and ensuring correct sequencing.

Core Features & Use Cases

  • Guides users through selecting the change to continue when multiple changes exist, checks status, and retrieves required instructions for the next artifact.
  • Creates the next artifact from a schema-driven template while honoring dependencies and completed artifacts.
  • Use Case: A developer wants to progress an OpenSpec change by generating the next proposal/spec/design artifact in the proper order, without manual parsing of statuses.

Quick Start

Execute the OpenSpec continuation flow to generate the next artifact for the active 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 and generate the next artifact in the workflow?

To continue an OpenSpec change, the skill automates selecting the active change, checking its status, and creating the next artifact from a schema-driven template. It ensures artifacts are generated in the correct order while respecting dependencies and constraints.

What is the process for managing multi-artifact OpenSpec changes?

Managing multi-artifact OpenSpec changes involves sequentially creating proposals, specs, and designs. The skill retrieves required instructions for the next artifact and applies the provided template, ensuring correct sequencing without manual status parsing.

How does artifact sequencing work when progressing an OpenSpec change?

Artifact sequencing works by checking the completed artifacts and honoring dependencies before generating the subsequent artifact. The skill ensures the next proposal, spec, or design is created in the proper order using the defined template.

Can I automate OpenSpec change management when multiple changes exist?

Yes, you can automate OpenSpec change management when multiple changes exist. The skill guides users through selecting the specific change to continue, checks its current status, and retrieves the required instructions for the next artifact.

Do I need to manually check status to create the next OpenSpec artifact?

No, you do not need to manually check status to create the next OpenSpec artifact. The skill automates status checking and retrieves the required instructions, reducing manual coordination for the workflow continuation.

What are the limitations of automating OpenSpec change continuation?

The automation is limited to multi-artifact OpenSpec processes using provided templates. It cannot generate artifacts out of order and must respect dependencies and constraints, meaning previous artifacts must be completed before proceeding.