skills.rest
yun-s-oh
yun-s-ohCOMMUNITY
Explore all skills by this author →
GitHub

openspec-continue-change

Automate artifact creation in OpenSpec change workflows using the openspec CLI.

Updated May 29, 2026
Search Tags:#workflow automation#software development#change management#OpenSpec#artifact creation
One-click install
npx skills add https://github.com/yun-s-oh/ha-anker-solix-f2000 --skill openspec-continue-change-yun-s-oh
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-continue-change
Source: https://github.com/yun-s-oh/ha-anker-solix-f2000/tree/main/.agent/skills/openspec-continue-change
Command: npx skills add https://github.com/yun-s-oh/ha-anker-solix-f2000 --skill openspec-continue-change-yun-s-oh

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires openspec, and includes scripts (resource) components.

What problem does it solve?

This Skill helps users progress through OpenSpec changes by creating the next artifact, streamlining the workflow process.

Core Features & Use Cases

  • Artifact Creation: Automates the creation of the next artifact in an OpenSpec change workflow.
  • Change Management: Provides a structured approach to managing and progressing OpenSpec changes.
  • Use Case: Ideal for software development teams using OpenSpec to manage their code changes, allowing developers to quickly create the next artifact in their workflow.

Quick Start

To continue working on your OpenSpec change, use the 'continue-change' skill and specify the change name if known.

Frequently Asked Questions about openspec-continue-change

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

FAQPage Schema
How do I automate artifact creation in an OpenSpec workflow?▼

Automating artifact creation in an OpenSpec workflow is handled by prompting for change selection, checking the current status, and generating the next ready or complete artifact. This streamlines spec-driven schema workflows by automating the progression of code changes.

Do I need the openspec CLI to manage spec-driven schema changes?▼

Yes, the openspec CLI is required to manage spec-driven schema changes. The workflow depends on the openspec command line interface to check artifact status and execute the creation of the next artifact for your software development changes.

How does OpenSpec handle change status checks for artifact generation?▼

OpenSpec change status checks evaluate whether an artifact is marked complete or ready before acting. The workflow automation checks the current status of the specified change and then creates the appropriate next artifact based on that status.

Can I specify a change name to continue an OpenSpec workflow?▼

Yes, you can specify a change name to continue an OpenSpec workflow. Providing the change name directly streamlines the artifact creation process by bypassing the prompt for change selection and immediately checking that change's status.

What is the best way to streamline OpenSpec change management for development teams?▼

Streamlining OpenSpec change management is best achieved by automating the creation of the next artifact. This provides a structured approach for software development teams to progress through spec-driven schema workflows without manual artifact intervention.

Related Skills

Explore More Software Engineering Skills→
Soju06Soju06
2.6k

openspec-continue-change

Creates the next OpenSpec artifact from parsed status and templates via the openspec CLI.

Community
Advanced
inflexa-aiinflexa-ai
29

openspec-continue-change

Orchestrate OpenSpec change lifecycle status checks and sequential artifact generation.

Official
Advanced
joannanowakowskajoannanowakowska

openspec-continue-change

Create the next required artifact in an OpenSpec change workflow.

Community
Advanced
pertrai1pertrai1

openspec-new-change

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

Community
Intermediate