openspec-continue-change

Guide OpenSpec change progression by selecting a change and creating the next artifact.

Updated Apr 22, 2026
One-click install
npx skills add https://github.com/dentedgem9846-claw/chronocrystal-opsx --skill openspec-continue-change-dentedgem9846-claw
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-continue-change
Source: https://github.com/dentedgem9846-claw/chronocrystal-opsx/tree/main/.pi/skills/openspec-continue-change
Command: npx skills add https://github.com/dentedgem9846-claw/chronocrystal-opsx --skill openspec-continue-change-dentedgem9846-claw

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Continue working on an OpenSpec change by creating the next artifact. Use when the user wants to progress their change, create the next artifact, or continue their workflow.

Core Features & Use Cases

  • Orchestrates OpenSpec change progression by guiding the user through selecting the change, checking status, and creating the next artifact.
  • Enforces artifact creation order, dependency awareness, and progress tracking to ensure consistency across the OpenSpec workflow.
  • Provides guardrails and prompts to avoid ambiguity, and reads completed artifacts to contextualize new work.

Quick Start

Tell me the OpenSpec change you want to continue, and I will guide you through selecting it and creating 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 workflow and create the next artifact?

To continue an OpenSpec change, you select the change, check its status, and generate the next artifact in the correct sequence. The workflow reads completed artifacts to contextualize new work and ensures dependency awareness.

What is the correct sequence for creating artifacts in an OpenSpec change?

Artifact creation order in OpenSpec is enforced by checking the change status and reading dependencies. This ensures artifacts are generated sequentially, maintaining consistency and avoiding ambiguity across the workflow.

Do I need the openspec CLI to manage change progression and artifact generation?

Yes, you need the openspec CLI installed to manage change progression. It requires access to relevant change data to read dependencies and write the next artifact in the workflow sequence.

How does dependency awareness work when progressing an OpenSpec change?

Dependency awareness works by reading completed artifacts and checking the change status before generating new work. This contextualizes the next artifact and enforces the correct creation order within the OpenSpec workflow.

Can I skip steps when creating artifacts for an OpenSpec change?

No, you cannot skip steps. The workflow enforces artifact creation order and provides guardrails to avoid ambiguity, ensuring each artifact is generated sequentially based on dependency awareness and progress tracking.