openspec-continue-change

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

Updated Aug 7, 2026
One-click install
npx skills add https://github.com/javakishore-veleti/lifting-diary-app --skill openspec-continue-change-javakishore-veleti
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-continue-change
Source: https://github.com/javakishore-veleti/lifting-diary-app/tree/main/.qwen/skills/openspec-continue-change
Command: npx skills add https://github.com/javakishore-veleti/lifting-diary-app --skill openspec-continue-change-javakishore-veleti

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When working through an OpenSpec change, it is easy to lose track of which artifact comes next, what its required structure is, and which dependencies must be read first. This Skill inspects the current change status and creates exactly the next ready artifact, keeping the spec-driven workflow moving without manual bookkeeping. ## Core Features & Use Cases - Status-driven progression: Runs openspec status to parse artifact states (done, ready, blocked) and picks the first ready artifact to create. - Template-guided artifact creation: Fetches per-artifact instructions, templates, rules, and dependency files via openspec instructions, then writes the artifact to the resolved output path. - Store and change selection: Supports named OpenSpec stores via --store <id> and helps disambiguate between multiple active changes by listing the most recently modified ones. - Use Case: You have a change with a completed proposal and want the design document next. Invoke the Skill, and it reads the proposal from disk, applies the schema's template and rules, writes the design artifact, and reports the updated progress. ## Quick Start Ask the assistant to continue your OpenSpec change, optionally naming the change, and it will create the next 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 workflow?

Invoke the Skill with an optional change name. It runs openspec status to find the first artifact marked ready, fetches its instructions and template, reads completed dependency files, and writes the new artifact to the resolved output path.

How does the Skill choose which change to work on?

It uses a provided name, infers from conversation context, or auto-selects when only one active change exists. If ambiguous, it lists the most recently modified changes from openspec list and asks you to pick, marking the newest as recommended.

Does it support multiple OpenSpec stores?

Yes. If you name a store, it runs openspec store list to discover registered store ids, then appends --store <id> to all commands that read or write specs and changes for the rest of the workflow.

What happens when all planning artifacts are complete?

When isPlanningComplete is true, the Skill stops creating artifacts, shows the final status with the schema used, and suggests implementing the change and archiving it once implementation work is done.

Why does it re-read dependency files from disk?

Files may have been edited since they were last seen in conversation. Re-reading from disk guarantees the new artifact is built on the current content of its completed dependencies rather than stale context.