openspec-continue-change

Generates the next OpenSpec artifact from CLI status and dependency context.

Updated Jan 23, 2026

Search Tags:#automation #workflow #CLI #artifact #change-management #open spec

Ready to run

npx skills add https://github.com/hossam7amdy/easy-auth --skill openspec-continue-change-hossam7amdy

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: openspec-continue-change
Source: https://github.com/hossam7amdy/easy-auth/tree/main/.agent/skills/openspec-continue-change
Command: npx skills add https://github.com/hossam7amdy/easy-auth --skill openspec-continue-change-hossam7amdy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you advance an OpenSpec change by automatically producing the next artifact in the workflow, eliminating manual tracking and ensuring alignment with the chosen schema.

Core Features & Use Cases

Artifact orchestration: Proceeds through the OpenSpec artifact sequence, creating the next artifact based on the current state.
Status-driven workflow: Reads the OpenSpec CLI status to decide what to generate next and what dependencies to consider.
Guided execution: Provides structured instructions and validations to maintain orderly progression across changes.

Quick Start

Begin by checking the current status of your change: openspec status --change "<change-name>" --json Then, provide or select the change name to proceed with generating 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 automate creating the next artifact in an OpenSpec change workflow?▼

To automate OpenSpec change progression, you read the CLI status output to identify the current state, then apply dependency context to generate the subsequent artifact file according to the schema's rules and templates.

What does the OpenSpec CLI status command do for change management?▼

The OpenSpec CLI status command outputs the current state of a change in JSON format, which determines what artifact to generate next and identifies dependencies required for advancing the change sequence.

How do I advance an OpenSpec change to the next step using CLI?▼

You advance an OpenSpec change by providing the change name, which reads the CLI status, applies dependency context, and creates the next artifact file to unlock subsequent workflow steps.

Do I need to manually track artifact sequences in OpenSpec?▼

No, manual tracking is eliminated. The skill reads the CLI status output to orchestrate the artifact sequence automatically, ensuring alignment with the chosen schema and maintaining orderly progression.

Can I use this OpenSpec workflow automation without any dependencies?▼

Yes, the skill operates with no external dependencies. It relies solely on reading the OpenSpec CLI status outputs and applying the schema's rules and templates to guide artifact generation.