openspec-continue-change

Generate the next OpenSpec artifact in sequence from current status.

149|22|Updated Mar 6, 2026
One-click install
npx skills add https://github.com/luzhenqian/ai-coding-lab --skill openspec-continue-change-luzhenqian
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-continue-change
Source: https://github.com/luzhenqian/ai-coding-lab/tree/main/agent/dev-bot/.claude/skills/openspec-continue-change
Command: npx skills add https://github.com/luzhenqian/ai-coding-lab --skill openspec-continue-change-luzhenqian

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides a guided, repeatable process to continue an OpenSpec change by creating the next artifact, ensuring consistent progress and reducing context switching.

Core Features & Use Cases

  • Step-by-step workflow for selecting a change, checking status, and generating the next artifact in the OpenSpec sequence.
  • Enforces guardrails such as one artifact per invocation, dependency awareness, and explicit user confirmation to proceed.
  • Use Case: When a team wants to advance an OpenSpec change, this skill orchestrates the next artifact creation and maintains ordering.

Quick Start

Ask me to continue the change by creating 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 continue an OpenSpec change and generate the next artifact?

To continue an OpenSpec change, this skill prompts for change selection when ambiguous and generates the next artifact in sequence based on the current status. It reads dependencies from completed artifacts and writes new artifacts to specified output paths using provided templates.

What is the OpenSpec workflow for sequential artifact creation?

The OpenSpec workflow involves progressing a change by creating artifacts in sequence. This skill enforces guardrails like one artifact per invocation, dependency awareness, and explicit user confirmation to maintain consistent ordering and reduce context switching.

Can I generate multiple OpenSpec artifacts in a single run?

No, you cannot generate multiple artifacts in a single run. The skill enforces a guardrail of one artifact per invocation to ensure explicit user confirmation and maintain strict dependency awareness throughout the OpenSpec change sequence.

How does dependency awareness work when progressing an OpenSpec change?

Dependency awareness works by reading dependencies from previously completed artifacts before generating the next one. This ensures the OpenSpec workflow maintains correct ordering and that the new artifact properly builds upon existing change context.

Do I need to specify output paths and templates for OpenSpec artifacts?

Yes, the skill uses provided templates and writes artifacts to specified output paths. This guided process ensures repeatable artifact creation and consistent progress within the OpenSpec change management workflow without manual file configuration.