skills.rest
alexei-lexx
alexei-lexxCOMMUNITY
Explore all skills by this author →
GitHub

openspec-continue-change

Generate the next artifact in an OpenSpec change workflow using the openspec CLI.

Updated Jun 4, 2025
Search Tags:#automation#workflow#cli#artifacts#developer-tools#openspec#change-management
One-click install
npx skills add https://github.com/alexei-lexx/budget --skill openspec-continue-change-alexei-lexx
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-continue-change
Source: https://github.com/alexei-lexx/budget/tree/main/.gemini/skills/openspec-continue-change
Command: npx skills add https://github.com/alexei-lexx/budget --skill openspec-continue-change-alexei-lexx

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you pick up an OpenSpec change and automatically generate the next artifact to advance the workflow, reducing context switching and manual drafting.

Core Features & Use Cases

  • Artifact progression: Detects READY artifacts and creates the next artifact file using the openspec CLI.
  • Dependency-aware: Reads completed artifacts to ensure correct context and order.
  • Guardrails: Prompts when needed to specify the change or when ambiguity exists.

Quick Start

Create the next artifact for the selected OpenSpec change by following the prompts and generating the first ready artifact file according to the instructions.

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 workflow artifact?▼

To continue an OpenSpec change, the workflow detects the next READY artifact, reads completed artifacts for context, and uses the openspec CLI to generate the target artifact file according to the defined schema-specific sequence.

How does dependency-aware artifact progression work in an OpenSpec workflow?▼

Dependency-aware progression works by reading completed artifacts to ensure correct context and order before generating the next file, enforcing the schema-specific artifact sequence for multi-artifact OpenSpec changes.

What is the best way to automate creating the next artifact in a multi-artifact change management workflow?▼

The best way to automate creating the next artifact is using the openspec CLI to advance the change, which reduces manual drafting and context switching by automatically generating the next ready artifact file.

When do I need to specify the OpenSpec change manually during artifact generation?▼

You need to specify the change manually when ambiguity exists in the workflow, triggering built-in guardrails that prompt for clarification to ensure the correct artifact is generated for the target OpenSpec change.

Does the openspec CLI support enforcing a specific artifact sequence for changes?▼

Yes, the openspec CLI supports enforcing a schema-specific artifact sequence, ensuring correct order and dependency awareness when generating the next artifact for multi-artifact OpenSpec changes.

Related Skills

Explore More Software Engineering Skills→
jaxxstormjaxxstorm
4

openspec-continue-change

Create the next OpenSpec change artifact via the openspec CLI.

Community
Advanced
danielsogldanielsogl
39

openspec-new-change

Scaffold OpenSpec changes with schema-aware artifact workflow instructions.

Community
Advanced
memorysavermemorysaver

openspec-ff-change

Generate OpenSpec change artifacts in dependency order via the openspec CLI.

Community
Advanced
luzhenqianluzhenqian
149

openspec-ff-change

Generate all OpenSpec artifacts for a specified change with dependency-aware sequencing.

Community
Advanced