openspec-continue-change

Create the next pending OpenSpec artifact from JSON status output.

Updated Aug 23, 2026

Search Tags:#automation #workflow #schema #cli #openspec #artifact

Ready to run

npx skills add https://github.com/brianzzs/GreenFiveInnings --skill openspec-continue-change-brianzzs

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: openspec-continue-change
Source: https://github.com/brianzzs/GreenFiveInnings/tree/main/.opencode/skills/openspec-continue-change
Command: npx skills add https://github.com/brianzzs/GreenFiveInnings --skill openspec-continue-change-brianzzs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It streamlines the workflow of advancing OpenSpec changes by automatically determining the next pending artifact and generating it, eliminating manual tracking and command handling.

Core Features & Use Cases

Change Selection: Prompts the user to choose the appropriate change when ambiguous.
Status Evaluation: Checks the current state of artifacts and identifies the next ready artifact.
Artifact Creation: Generates the artifact using provided templates, respecting context and rules.
Progress Tracking: Updates and displays progress after each creation.

Quick Start

Ask the skill to continue the current OpenSpec change and create the next artifact.

Frequently Asked Questions about openspec-continue-change

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

FAQPage Schema

How do I automatically generate the next pending artifact in an OpenSpec workflow?▼

You can automatically generate the next OpenSpec artifact by prompting the skill to continue the current change. It evaluates the JSON status output from the openspec CLI to identify and create the next pending artifact using predefined templates.

How do I track progress and create artifacts step by step using the openspec CLI?▼

To track progress and create artifacts step by step, the skill parses JSON status outputs from the openspec CLI. After generating an artifact using provided templates, it updates and displays the current progress of the schema-driven change.

Do I need the openspec CLI installed to generate schema-driven change artifacts?▼

Yes, you need the openspec CLI installed to generate schema-driven change artifacts. The skill requires the CLI to parse JSON status outputs and determine the next pending artifact in the workflow.

What happens when the OpenSpec change selection is ambiguous during artifact generation?▼

When the OpenSpec change selection is ambiguous, the skill prompts the user to choose the appropriate change. This ensures the correct status evaluation and artifact creation occurs for the intended schema-driven workflow.

How does automatic artifact generation handle context and rules in OpenSpec workflows?▼

Automatic artifact generation in OpenSpec workflows respects context and rules by applying provided template instructions. The skill evaluates the current state of artifacts to ensure the next generated file aligns with the schema-driven change requirements.

Why is my OpenSpec artifact not generating correctly during a schema-driven change?▼

Your OpenSpec artifact may not generate correctly if the JSON status output from the openspec CLI cannot be parsed or if the template instructions are not properly configured. The skill relies on these inputs to identify and create the next pending artifact.