skills.rest
manishsinghmf
manishsinghmfCOMMUNITY
Explore all skills by this author →
GitHub

openspec-continue-change

Generate the next OpenSpec artifact from ready artifacts using templates.

Updated Apr 15, 2026
Search Tags:#automation#workflow#cli#instructions#openspec#artifact#change-management
One-click install
npx skills add https://github.com/manishsinghmf/blink-with-anti --skill openspec-continue-change-manishsinghmf
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-continue-change
Source: https://github.com/manishsinghmf/blink-with-anti/tree/main/.cursor/skills/openspec-continue-change
Command: npx skills add https://github.com/manishsinghmf/blink-with-anti --skill openspec-continue-change-manishsinghmf

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Continue working on a change by creating the next artifact.

Core Features & Use Cases

  • Prompt for change selection if multiple changes exist
  • Check current status of the OpenSpec changes and artifacts
  • Create the next artifact from the FIRST ready artifact using the provided template and constraints
  • Enforce guardrails: one artifact per invocation, read dependencies, and show progress
  • Iterate by reporting unlocked artifacts after creation

Quick Start

Provide a change name to continue the OpenSpec workflow and create 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 create the next artifact?▼

To continue an OpenSpec change, the workflow selects the change, fetches its status, and generates the next artifact from the first ready artifact using templates. It displays progress and shows newly unlocked artifacts.

How does OpenSpec change management enforce sequential artifact creation?▼

OpenSpec change management enforces sequential artifact creation by applying guardrails that restrict generation to one artifact per invocation and reading dependencies to ensure readiness before creating the next proposal, spec, design, or tasks.

Can I generate multiple OpenSpec artifacts in a single workflow invocation?▼

No, you cannot generate multiple artifacts in one invocation. OpenSpec workflow guardrails enforce creating exactly one artifact per execution to strictly maintain sequential artifact creation and progress integrity.

What is the best way to track OpenSpec change status and artifact readiness?▼

Tracking OpenSpec change status is handled by the CLI-driven workflow, which fetches the current status of changes and artifacts, displays progress, and reports unlocked artifacts after each generation step.

Do I need a CLI environment to automate OpenSpec workflow artifact generation?▼

Yes, you need a CLI environment to automate OpenSpec workflow artifact generation. The workflow is CLI-driven, requiring you to select the change and fetch its status to generate the next artifact from ready dependencies.

Related Skills

Explore More Software Engineering Skills→
jankneumannjankneumann
4

openspec-new-change

Scaffold a new OpenSpec change workflow with schema selection and status checks.

Community
Intermediate
hiro1989hiro1989
1

openspec-continue-change

Creates the next OpenSpec artifact (proposal, spec, design, or task) via CLI.

Community
Advanced
MeetTechnologyMeetTechnology

openspec-continue-change

Automate OpenSpec change progression by generating the next artifact via CLI.

Community
Advanced
ywh0606ywh0606

opsx-ff-change

Create OpenSpec implementation artifacts from feature requests using the openspec CLI.

Community
Intermediate