openspec-continue-change

Create the next OpenSpec artifact according to the active schema.

113|19|Updated Apr 8, 2025
One-click install
npx skills add https://github.com/goern/forgejo-mcp --skill openspec-continue-change-goern
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-continue-change
Source: https://github.com/goern/forgejo-mcp/tree/main/.claude/skills/openspec-continue-change
Command: npx skills add https://github.com/goern/forgejo-mcp --skill openspec-continue-change-goern

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps you continue an OpenSpec change by automatically creating the next artifact, coordinating with the current change context, dependencies, and artifact pipeline.

Core Features & Use Cases

  • Continue an OpenSpec workflow by selecting a change, verifying statuses, and creating the next artifact according to the active schema.
  • Read dependencies from completed artifacts to ensure consistency before writing the new artifact.
  • Handle ambiguous contexts by prompting for the specific change to continue.

Quick Start

Open an OpenSpec-enabled project and follow these steps:

  • Check current status: openspec status --change "<name>" --json
  • Create the next artifact: openspec instructions <artifact-id> --change "<name>" --json
  • If multiple changes exist, select the one you want to continue.

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?

Creating the next OpenSpec artifact involves selecting a change, checking its status, and following the active schema instructions. The process reads dependency artifacts to maintain consistency and prompts for user decisions when context is unclear before writing the output.

What happens if there are multiple OpenSpec changes in my project?

If multiple changes exist, the system prompts you to explicitly select the specific change to continue. This disambiguation step ensures that the next artifact is correctly mapped to the intended change context and dependency pipeline.

How does the OpenSpec workflow handle artifact dependencies?

Before writing a new artifact, the workflow reads dependent artifacts that are already completed. This ensures the new output strictly adheres to the active schema and maintains data consistency across the entire change pipeline.

Do I need to manually specify the output path for an OpenSpec artifact?

You do not need to manually set the output path. The workflow automatically writes the newly created artifact to the path specified by the instructions generated from the active OpenSpec schema, automating file placement.

When does OpenSpec prompt for user decisions during artifact creation?

The workflow prompts for user input when the context is ambiguous, such as when multiple changes are active simultaneously. This ensures you select the correct change before it reads dependencies and writes the next artifact.