openspec-continue-change

Generate the next OpenSpec artifact for an active change.

Updated Mar 9, 2025
One-click install
npx skills add https://github.com/rock-hu/vitamin-compose --skill openspec-continue-change-rock-hu
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-continue-change
Source: https://github.com/rock-hu/vitamin-compose/tree/main/.qwen/skills/openspec-continue-change
Command: npx skills add https://github.com/rock-hu/vitamin-compose --skill openspec-continue-change-rock-hu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Continue working on an OpenSpec change by creating the next artifact. This Skill streamlines progressing an OpenSpec change by automatically generating the subsequent artifact in the standard OpenSpec workflow.

Core Features & Use Cases

  • Progress OpenSpec changes by creating the next artifact in the sequence for any active change.
  • Guide artifact creation based on the current status and schema, ensuring tasks remain in order.
  • Facilitate collaboration by keeping all stakeholders aligned as the change evolves from proposal to artifacts.

Quick Start

Use the openspec-continue-change command to generate the next artifact for the active OpenSpec change. If prompted, follow the CLI guidance to select the change, review dependencies, and confirm artifact creation.

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?

To continue an OpenSpec change, this skill automates generating the next artifact by evaluating the current status, identifying dependencies, and creating the subsequent artifact in the standard workflow sequence.

What is the standard workflow for OpenSpec artifact generation?

OpenSpec artifact generation follows a sequential workflow that progresses changes from proposal through design, specs, and tasks, ensuring dependency awareness and traceability across each generated artifact.

How do I use the openspec CLI to progress a change?

You can use the openspec CLI to progress a change by invoking the continue command, which guides you through selecting the active change, reviewing dependencies, and confirming the next artifact creation.

Does OpenSpec enforce sequential artifact creation for changes?

Yes, OpenSpec enforces sequential artifact generation by checking the latest status and schema dependencies, ensuring that subsequent artifacts are only created when prerequisite work is complete.

Can I skip artifacts when progressing an OpenSpec change?

No, this skill enforces sequential artifact generation with dependency awareness, meaning you cannot skip artifacts and must progress through the standard workflow order to maintain traceability.

What dependencies are required to automate OpenSpec change continuation?

Automating OpenSpec change continuation requires the openspec CLI environment, as the skill uses it to evaluate current change status, apply schema rules, and generate the next artifact without external dependencies.