openspec-continue-change

Generate the next required OpenSpec artifact according to a workflow schema.

7|3|Updated Dec 24, 2023
One-click install
npx skills add https://github.com/Pony-Unicorn/react-template --skill openspec-continue-change-pony-unicorn
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-continue-change
Source: https://github.com/Pony-Unicorn/react-template/tree/main/.opencode/skills/openspec-continue-change
Command: npx skills add https://github.com/Pony-Unicorn/react-template --skill openspec-continue-change-pony-unicorn

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill streamlines the development workflow for OpenSpec changes by automating the creation of the next required artifact, ensuring a consistent and guided progression through the defined process.

Core Features & Use Cases

  • Automated Artifact Generation: Creates the next logical artifact (e.g., proposal, spec, design, tasks) based on the current state of an OpenSpec change.
  • Workflow Adherence: Ensures changes follow the defined OpenSpec schema sequence, preventing out-of-order creation.
  • Use Case: After defining a new feature proposal using OpenSpec, you can use this Skill to automatically generate the corresponding specification file, then later use it again to create the design document, and so on, until the change is fully implemented.

Quick Start

Continue the OpenSpec change named 'user-authentication-flow'.

Frequently Asked Questions about openspec-continue-change

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate OpenSpec artifact generation for the next development phase?

Automated OpenSpec artifact generation works by validating the current change status and programmatically creating the next required artifact, such as a proposal, specification, design document, or task list, based on a specified workflow schema.

What is the best way to ensure my spec-driven workflow follows the correct artifact sequence?

To ensure your spec-driven workflow follows the correct artifact sequence, this process validates current status and enforces artifact dependencies, preventing out-of-order creation of proposals, specifications, and design documents.

How do I create the next specification or design document after defining an OpenSpec feature proposal?

After defining an OpenSpec feature proposal, you can create the next specification or design document by triggering the continuous progression mechanism, which identifies and generates the next required artifact in the workflow schema.

How does the OpenSpec change progression mechanism handle ambiguous artifact states?

When the OpenSpec change progression mechanism encounters ambiguous artifact states, it validates the current workflow status and prompts the user for selection to ensure proper adherence to artifact dependencies and order.

Can I use this workflow schema validation for complex spec-driven development processes?

Yes, this workflow schema validation supports complex spec-driven development processes by continuously progressing changes and programmatically creating required artifacts like proposals, specifications, design documents, and task lists.

What are the limitations of automating OpenSpec change progression?

The primary limitation of automating OpenSpec change progression is that it requires a specified workflow schema to determine the next artifact, and it pauses to prompt the user for selection when the current status is ambiguous.