openspec-continue-change

Generate the next OpenSpec change artifact from status and templates.

4|Updated Oct 10, 2025
One-click install
npx skills add https://github.com/JanuaryLabs/deepagents --skill openspec-continue-change-januarylabs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-continue-change
Source: https://github.com/JanuaryLabs/deepagents/tree/main/.claude/skills/openspec-continue-change
Command: npx skills add https://github.com/JanuaryLabs/deepagents --skill openspec-continue-change-januarylabs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes the friction of progressing an OpenSpec change by automating selection, status inspection, and creation of the next required artifact so users do not have to manually coordinate CLI calls, parse JSON, or manage artifact templates.

Core Features & Use Cases

  • Guided change selection: Prompts the user to pick a change from the most recently modified options and marks a recommended choice.
  • Status inspection and decisioning: Runs openspec status to determine which artifacts are ready, blocked, or complete and chooses the next artifact to produce.
  • Artifact generation: Fetches artifact instructions, reads completed dependency files for context, fills the provided template respecting context and rules, writes the artifact to the specified output path, and reports progress and unlocked artifacts.
  • Use case: Move a proposal forward into a spec or design artifact in a spec-driven workflow by asking the assistant to continue a specific change.

Quick Start

Ask the assistant to continue your OpenSpec change by saying "Continue my change named <change-name> 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 create the next artifact for an OpenSpec change?

To create the next artifact for an OpenSpec change, you ask the assistant to continue a specific change. The skill selects the change, inspects its status via the openspec CLI, and automatically generates the next required artifact using the proper template.

How does spec-driven change management work with OpenSpec?

Spec-driven change management with OpenSpec progresses changes through ordered artifacts. The skill reads completed dependency files for context, fills the provided template respecting schema rules, writes the output file, and reports which subsequent artifacts are unlocked.

Do I need the openspec CLI to generate spec artifacts?

Yes, you need the openspec CLI with JSON output enabled to generate spec artifacts. The skill requires CLI access to inspect artifact status and determine which outputs are ready, blocked, or complete before composing the next file.

What's the best way to automate proposal progression in a spec-driven workflow?

Automating proposal progression is handled by prompting the assistant to continue a named change. The skill automatically coordinates CLI calls, parses JSON status responses, reads dependencies, and fills artifact templates to move your proposal forward into a spec or design document.

Why is my OpenSpec change artifact blocked from generation?

An OpenSpec change artifact is blocked when preceding dependencies are not yet complete. The skill runs openspec status to check readiness, and it will only choose and generate the next artifact that is currently ready while skipping those marked as blocked.

Can I use OpenSpec change management without manually parsing JSON status output?

Yes, you can progress changes without manually parsing JSON because the skill automates status inspection and decisioning. It reads the JSON output from the openspec CLI internally to determine the next artifact and manages the template filling process for you.