openspec-continue-change

Create the next OpenSpec change artifact in the correct sequence.

Updated Feb 4, 2026
One-click install
npx skills add https://github.com/SQDR2/PortableConversationScriptAssistant --skill openspec-continue-change-sqdr2
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-continue-change
Source: https://github.com/SQDR2/PortableConversationScriptAssistant/tree/main/.github/skills/openspec-continue-change
Command: npx skills add https://github.com/SQDR2/PortableConversationScriptAssistant --skill openspec-continue-change-sqdr2

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill guides users to seamlessly progress an OpenSpec change by selecting the current change, assessing its status, and generating the next artifact in the correct sequence, preventing out-of-order work.

Core Features & Use Cases

  • Guided change progression: prompts to pick the most recently modified change and confirms readiness before creating an artifact.
  • Status-driven workflow: reads OpenSpec status to determine the next actionable artifact and its dependencies.
  • Artifact creation with guards: creates one artifact per invocation using the schema's template, while honoring dependencies and restrictions.
  • Educational prompts: explains the workflow and options to the user, reducing confusion for new OpenSpec users.

Quick Start

Ask OpenSpec to continue the current change by selecting the most recent ready artifact and generating it according to the active workflow.

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 create the next artifact?

To continue an OpenSpec change, the workflow identifies your current change, checks its status for dependencies, and generates the next artifact in the correct sequence using the active schema template.

How does OpenSpec determine the next actionable artifact in a workflow?

OpenSpec determines the next actionable artifact by reading the change status, evaluating readiness, and checking dependencies to enforce guardrails that prevent out-of-order artifact creation.

Can I generate multiple artifacts at once during an OpenSpec change?

No, the workflow creates one artifact per invocation to maintain sequence integrity, honoring dependencies and schema restrictions while prompting for input when context is ambiguous.

What's the best way to select a specific OpenSpec change to work on?

The best way to select an OpenSpec change is through the guided progression prompt, which presents the top recently modified changes for you to choose from before assessing status.

Why does OpenSpec prompt me for input while generating an artifact?

OpenSpec prompts for input to resolve ambiguous context during artifact creation, serving as an educational guide that explains workflow options and reduces confusion for new users.

Do I need to manually check dependencies before creating an OpenSpec artifact?

No, you do not need to manually check dependencies because the status-driven workflow automatically reads OpenSpec status to determine readiness and enforce dependency restrictions before generating an artifact.