openspec-continue-change

Create the next OpenSpec change artifact via the openspec CLI.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill guides continuing an OpenSpec change by creating the next artifact in the sequence, enabling smooth progression of work without manual artifact orchestration.

Core Features & Use Cases

  • Coordinate progress through an OpenSpec change by checking status and generating the next artifact via the openspec CLI.
  • Enforce artifact order and dependency handling to prevent out-of-sequence work.
  • Provide guidance and templates to ensure consistent artifact structure across changes.

Quick Start

Run the recommended OpenSpec commands to inspect the current change state and initiate the creation of the next artifact, following the on-screen prompts to select changes or artifacts.

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, use the OpenSpec CLI to inspect the current change status and generate the next artifact in the sequence, ensuring proper dependency handling and artifact placement.

What is artifact sequencing in OpenSpec change management?

Artifact sequencing in OpenSpec change management is the process of advancing a change through a defined sequence of artifacts, enforcing order and dependency handling to prevent out-of-sequence work.

Do I need the OpenSpec CLI to automate workflow progression for changes?

Yes, you need the OpenSpec CLI to automate workflow progression, as it is required to check status, handle dependencies, and generate correctly placed artifacts during the change process.

How does this automation handle dependencies when advancing a change?

This automation handles dependencies by enforcing artifact order and checking the current change status before generating the next artifact, preventing out-of-sequence work and ensuring structural consistency.

Can I use templates to ensure consistent artifact structure across OpenSpec changes?

Yes, you can use provided templates to ensure consistent artifact structure across OpenSpec changes, as the process adheres to artifact templates and respects context and rules for correct placement.

What's the best way to prevent out-of-sequence work in OpenSpec change management?

The best way to prevent out-of-sequence work is to use automated CLI commands that enforce artifact order and dependency handling, checking the current status before generating the next artifact.