skills.rest
psacc
psaccCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

openspec-continue-change

Generate the next OpenSpec change artifact using the openspec CLI.

1|Updated Feb 24, 2026
Search Tags:#schema-driven#openspec#workflow-automation#change-management#artifact-generation#cli-guidance
One-click install
npx skills add https://github.com/psacc/omnisess --skill openspec-continue-change-psacc
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-continue-change
Source: https://github.com/psacc/omnisess/tree/main/.claude/skills/openspec-continue-change
Command: npx skills add https://github.com/psacc/omnisess --skill openspec-continue-change-psacc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Continuously progress an OpenSpec change by automatically creating the next required artifact, reducing manual steps and context switching.

Core Features & Use Cases

  • Automated generation of the next artifact in a change workflow using the openspec CLI.
  • Guided selection when multiple changes exist, ensuring correct sequencing and dependencies.
  • Template-driven artifact creation that respects constraints and existing artifacts.

Quick Start

Run openspec-continue-change to generate the next artifact for the current change, or specify a change name to target a specific item.

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

To proceed with schema-driven artifact creation, run openspec-continue-change to target a specific change or let it guide selection, ensuring correct sequencing and respecting existing artifacts through the openspec CLI.

How does schema-driven change management handle multiple active OpenSpec changes?▼

Schema-driven change management handles multiple active OpenSpec changes by providing guided selection, ensuring you target the correct item and maintain proper dependency sequencing before generating the next artifact.

Do I need the openspec CLI to use schema-driven artifact generation for change management?▼

Yes, you need the openspec CLI installed to use schema-driven artifact generation, as the workflow relies on it to enforce constraints, sequence dependencies, and generate template-based artifacts for your changes.

What are the limitations of automating OpenSpec change progression?▼

The main limitation of automating OpenSpec change progression is that it strictly respects template constraints, sequencing, and existing artifacts, meaning it cannot generate out-of-order artifacts or bypass defined workflow dependencies.

Related Skills

Explore More Software Engineering Skills→
afadhityaafadhitya
4

openspec-continue-change

Create OpenSpec workflow artifacts and track schema progress.

Community
Advanced
roger8broger8b

openspec-continue-change

Generate OpenSpec change artifacts to continue workflow progression.

Community
Intermediate
edwardsnjdedwardsnjd
9

openspec-new-change

Scaffold a new OpenSpec change directory using a workflow schema.

Community
Intermediate
pertrai1pertrai1

openspec-new-change

Initiate a new OpenSpec change and create essential artifacts via the openspec CLI.

Community
Intermediate