openspec-continue-change

Create the next OpenSpec change artifact in the proposal-to-tasks workflow.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/anaclumos/verifidia --skill openspec-continue-change-anaclumos
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-continue-change
Source: https://github.com/anaclumos/verifidia/tree/main/.opencode/skills/openspec-continue-change
Command: npx skills add https://github.com/anaclumos/verifidia --skill openspec-continue-change-anaclumos

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps engineers and product teams keep OpenSpec changes moving by guiding the creation of the next artifact in the workflow, ensuring incremental progress and clear continuity.

Core Features & Use Cases

  • Guides you to continue an OpenSpec change by generating the next artifact (proposal → specs → design → tasks) based on current state.
  • Enforces guardrails: prompts for change selection when multiple changes exist and reads status and instructions to determine the next actionable artifact.
  • Use Case: After completing a design, generate the next tasks artifact to continue implementation and tracking.

Quick Start

Instruct the system to continue the OpenSpec change by identifying the target change or letting context infer it, and it will 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 continue an OpenSpec change workflow from where I left off?

To continue an OpenSpec change, the Skill reads the current status and generates the next artifact in sequence, ensuring you pick up progress without restarting the workflow.

What is the correct artifact sequence for OpenSpec change management?

The OpenSpec change management sequence flows from proposal to specs, then to design, and finally to tasks, with the Skill enforcing prerequisites before each artifact is generated.

How do I generate the next artifact when multiple OpenSpec changes exist?

When multiple OpenSpec changes exist, the Skill prompts you to select the target change, then reads its status to determine and generate the exact next artifact needed.

Can I skip artifacts and jump straight to tasks in an OpenSpec workflow?

No, you cannot skip artifacts because the Skill enforces strict sequencing and validates prerequisites, ensuring each step from proposal to tasks is completed in order.

Does the OpenSpec change workflow require a CLI to generate artifacts?

Yes, the Skill uses CLI guidance documented in SKILL.md to validate prerequisites and produce the correct artifact structure for your OpenSpec change progression.