openspec-continue-change

Name: openspec-continue-change
Availability: InStock
Author: PBH-BTN

Generate the next OpenSpec workflow artifact via the OpenSpec CLI.

6.2k|152|Updated Feb 7, 2024

Search Tags:#automation #workflow #CLI #spec #openspec #artifact #project-management

Ready to run

npx skills add https://github.com/PBH-BTN/PeerBanHelper --skill openspec-continue-change-pbh-btn

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: openspec-continue-change
Source: https://github.com/PBH-BTN/PeerBanHelper/tree/main/.claude/skills/openspec-continue-change
Command: npx skills add https://github.com/PBH-BTN/PeerBanHelper --skill openspec-continue-change-pbh-btn

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates continuation of an OpenSpec workflow by generating the next artifact in the sequence, enabling users to progress their change without manual repetition.

Core Features & Use Cases

Create the next artifact in an OpenSpec workflow using the OpenSpec CLI.
Inspect current workflow status and dependencies to ensure correct ordering.
Automatically populate the artifact template and place it in the correct location for the active schema.

Quick Start

Use the OpenSpec CLI to continue the active change by generating the next artifact. If prompted for a change name, provide the exact change name and let the tool create the artifact file in the correct location as per the active schema.

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 in an OpenSpec workflow?▼

To generate the next OpenSpec artifact, the automation inspects the active workflow status and dependencies to determine the correct sequence, then automatically populates the artifact template and places it in the correct schema location.

How does OpenSpec CLI automation determine artifact ordering?▼

OpenSpec CLI automation determines artifact ordering by inspecting the current workflow status and honoring existing dependencies, ensuring the correct artifact is created in the proper sequence for the active schema.

What is the process to continue an OpenSpec change from proposal to implementation?▼

Continuing an OpenSpec change involves using the CLI to advance the workflow by generating the next artifact in the sequence, automatically progressing the proposal through implementation steps without manual repetition.

Do I need to manually create artifact files when using OpenSpec CLI workflow automation?▼

You do not need to manually create artifact files; the automation enforces CLI interaction to automatically populate the artifact template and place it in the correct location specified by the active schema.

What happens if dependencies are not met when advancing an OpenSpec workflow?▼

When advancing an OpenSpec workflow, the automation inspects current dependencies to ensure correct ordering, preventing the generation of the next artifact if the required preceding workflow dependencies are not satisfied.