skills.rest
kuchida1981
kuchida1981COMMUNITY
Explore all skills by this author →
GitHub

openspec-continue-change

Create the next required OpenSpec artifact after checking change status and dependencies.

Updated Mar 4, 2026
Search Tags:#workflow#spec-driven#cli#artifacts#change management#openspec
One-click install
npx skills add https://github.com/kuchida1981/discord-service-gateway --skill openspec-continue-change-kuchida1981
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-continue-change
Source: https://github.com/kuchida1981/discord-service-gateway/tree/main/.gemini/skills/openspec-continue-change
Command: npx skills add https://github.com/kuchida1981/discord-service-gateway --skill openspec-continue-change-kuchida1981

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you continue an existing OpenSpec workflow by selecting the right change, checking its status, and creating the next required artifact without breaking the sequence.

Core Features & Use Cases

  • Change Continuation: Resume work on an in-progress OpenSpec change from the most relevant next step.
  • Artifact Sequencing: Follows the required order of proposal, specs, design, and tasks so nothing is skipped.
  • Dependency-Aware Progression: Reads completed artifacts before generating the next one to keep outputs consistent.
  • Use Case: If a project already has a proposal and specs, this Skill can produce the next ready artifact and show what becomes unlocked afterward.

Quick Start

Ask me to continue an OpenSpec change, and I will inspect the available changes and create the next required artifact for you.

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 from where I left off?▼

To continue an OpenSpec change, the skill inspects available changes, checks the current status, and generates the next required artifact in the sequence. It reads completed dependencies to ensure consistent output and resumes the workflow seamlessly.

What is the required artifact sequence in an OpenSpec workflow?▼

The OpenSpec workflow requires sequential artifact creation: proposal, specs, design, and tasks. The skill enforces this ordered artifact handling to ensure nothing is skipped and dependencies are fully respected during progression.

Do I need the OpenSpec CLI installed to manage change progression?▼

Yes, the OpenSpec CLI is required to manage change progression. The skill relies on CLI access to inspect available changes, read completed dependencies, and generate the next required artifact in the spec-driven workflow.

How does dependency-aware progression work when creating specs and tasks?▼

Dependency-aware progression works by reading completed artifacts before writing the next file. This ensures the new spec or task artifact remains consistent with existing proposals and specs, preventing sequence breaks in the change management workflow.

Can I skip writing a proposal and start directly with design or tasks in OpenSpec?▼

No, you cannot skip artifacts in OpenSpec. The skill follows the strict order of proposal, specs, design, and tasks, applying status checks and dependency-aware progression to ensure all required artifacts are created sequentially.

Related Skills

Explore More Software Engineering Skills→
ondataondata
9

openspec-new-change

Initialize a new OpenSpec change with an artifact-driven workflow scaffold.

Official
Advanced
ZanebonoAlterZanebonoAlter
19

openspec-verify-change

Validate implementation completeness against delta specs before archiving.

Community
Advanced
wtg42wtg42

openspec-continue-change

Create the next OpenSpec change artifact from CLI status and dependencies.

Community
Intermediate
khapn-2933khapn-2933

tkm:manage-project

Track tasks, manage dependencies, and generate status reports for multi-agent projects.

Community
Advanced