openspec-continue-change

Generate the next OpenSpec change artifact using a framework template.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill automates the continuation workflow for OpenSpec changes by generating the next artifact, enabling teams to progress changes without manual drafting.

Core Features & Use Cases

  • Guided continuation: prompts for change selection when needed and creates the next artifact in the sequence.
  • Dependency-aware: reads completed artifacts to ensure correct order and consistency.
  • Template-driven output: uses a defined template to structure the new artifact in the correct location.

Quick Start

Provide the change name when prompted to continue and let OpenSpec generate 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 generate the next artifact for an ongoing OpenSpec change?

To generate the next artifact for an OpenSpec change, you provide the change name, and the workflow automatically reads dependencies and creates the next artifact in the sequence.

What is the artifact sequence for OpenSpec change management?

The OpenSpec change management workflow enforces a non-skippable artifact sequence, reading previously completed dependency artifacts before writing the next one to ensure consistency.

How does dependency-aware artifact generation work in OpenSpec?

Dependency-aware artifact generation works by reading completed artifacts before creation, enforcing a strict sequence to ensure the next artifact maintains consistency across multiple changes.

Can I skip artifact creation steps when tracking an OpenSpec change?

You cannot skip artifact creation steps when tracking an OpenSpec change, because the workflow enforces a non-skippable sequence and requires reading dependency artifacts before creation.

Do I need to manually draft artifacts to continue an OpenSpec change?

You do not need to manually draft artifacts to continue an OpenSpec change, because the automated workflow uses a framework-provided template to write artifacts to the correct path.