skills.rest
beliciobcardoso
beliciobcardosoCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

openspec-continue-change

Creates the next artifact in an OpenSpec change workflow using the openspec CLI.

Updated Mar 17, 2026
Search Tags:#spec-driven#cli#tasks#openspec#proposal#artifact generation#change workflow
One-click install
npx skills add https://github.com/beliciobcardoso/mcp-postgres --skill openspec-continue-change-beliciobcardoso
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-continue-change
Source: https://github.com/beliciobcardoso/mcp-postgres/tree/main/.qwen/skills/openspec-continue-change
Command: npx skills add https://github.com/beliciobcardoso/mcp-postgres --skill openspec-continue-change-beliciobcardoso

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When working on spec-driven changes with OpenSpec, it is easy to lose track of which artifact comes next. This Skill inspects the current change status and creates exactly the next required artifact, keeping the workflow moving without manual bookkeeping. ## Core Features & Use Cases - Status-Driven Progression: Runs openspec status to determine which artifact is ready and creates only that one, never skipping steps. - Interactive Change Selection: Lists recent changes via openspec list --json and prompts the user to pick one when no change name is given. - Template-Guided Authoring: Fetches per-artifact instructions, templates, and dependency context from the CLI to produce correctly structured files like proposal.md, specs, design.md, and tasks.md. - Use Case: You drafted a proposal for a new API feature yesterday. Ask the assistant to continue the change, and it reads the proposal, generates the capability spec files, and reports progress (e.g., 2/4 artifacts complete). ## Quick Start Ask the assistant to continue working on your OpenSpec change and create the next artifact for the change you name.

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 workflow?▼

Provide the change name, or let the assistant list recent changes with openspec list --json so you can pick one. It then checks status, fetches instructions for the next ready artifact, and creates that single file.

What artifacts does the spec-driven schema create?▼

The spec-driven schema produces proposal.md, one spec.md per capability under specs/, design.md, and tasks.md in sequence. Each artifact is created only after its dependencies are complete.

Does this skill require the openspec CLI installed?▼

Yes, the skill depends entirely on the openspec CLI for listing changes, checking status, and retrieving artifact instructions. Without the CLI available in the environment, none of the workflow steps can execute.

Can it create multiple artifacts in one run?▼

No, the skill deliberately creates exactly one artifact per invocation and then stops. This guardrail ensures each artifact is reviewed and dependencies are read before the next step.

What happens if all artifacts are already complete?▼

When openspec status reports isComplete as true, the skill congratulates the user, shows the final status and schema used, and suggests implementing or archiving the change instead of creating anything new.

Related Skills

Explore More Software Engineering Skills→
NEETROFNEETROF
4

openspec-explore

Explores ideas, investigates codebases, and clarifies requirements before creating OpenSpec change proposals.

Official
Intermediate
PBH-BTNPBH-BTN
6.2k

openspec-bulk-archive-change

Archives multiple completed OpenSpec changes with conflict detection and spec synchronization.

Official
Advanced
zdpkzdpk

openspec

Manage OpenSpec change artifacts and validate progress with the OpenSpec CLI.

Community
Intermediate
qte77qte77
2

generating-tech-spec

Generate MADR/ADR, RFC, and design documents from input topics.

Community
Advanced