openspec-continue-change

Create the next artifact in an OpenSpec change lifecycle.

Updated Feb 6, 2024

Search Tags:#automation #workflow #guidance #status #openspec #artifact #change-management

Ready to run

npx skills add https://github.com/081595/mynode --skill openspec-continue-change-081595

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: openspec-continue-change
Source: https://github.com/081595/mynode/tree/main/myproject/.github/skills/openspec-continue-change
Command: npx skills add https://github.com/081595/mynode --skill openspec-continue-change-081595

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Continue working on a change by creating the next artifact within the OpenSpec workflow, helping teams progress without restarting from scratch.

Core Features & Use Cases

Seamlessly continue an in-progress OpenSpec change by generating the next artifact in the lifecycle.
Orchestrate status checks and instruction retrieval to guide artifact creation in the correct order.
Enforce dependency awareness and guardrails to ensure artifacts are produced in sequence.

Quick Start

Ask OpenSpec to continue the current change by generating the next artifact and guiding you through the required steps.

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 in-progress OpenSpec change without restarting?▼

To continue an OpenSpec change, the workflow automates progression by generating the next lifecycle artifact, allowing teams to resume seamlessly without restarting from scratch.

What is the OpenSpec change lifecycle workflow?▼

The OpenSpec change lifecycle is a strict artifact sequencing workflow that orchestrates status checks and instruction retrieval to guide context-aware artifact creation in the correct dependency order.

Can I generate artifacts out of order in an OpenSpec change workflow?▼

No, the OpenSpec change workflow enforces dependency awareness and guardrails to ensure artifacts are produced in sequence, preventing out-of-order generation across the lifecycle stages.

How do I check the status of an OpenSpec change to find the next artifact?▼

The workflow orchestrates status checks and instruction retrieval to determine the current lifecycle stage, automatically guiding you to create the next required artifact in the sequence.

When do I need automated artifact sequencing for change management?▼

Automated artifact sequencing is needed when managing multi-stage OpenSpec changes where strict dependency awareness and context-aware generation are required to produce artifacts in the correct order.