openspec-continue-change

Generate the next OpenSpec change artifact using the OpenSpec CLI.

Updated Jan 30, 2026
One-click install
npx skills add https://github.com/SimplifyMyCloud/gcp-bq-no-egress-dashboard-poc --skill openspec-continue-change-simplifymycloud
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-continue-change
Source: https://github.com/SimplifyMyCloud/gcp-bq-no-egress-dashboard-poc/tree/main/.claude/skills/openspec-continue-change
Command: npx skills add https://github.com/SimplifyMyCloud/gcp-bq-no-egress-dashboard-poc --skill openspec-continue-change-simplifymycloud

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Continue working on an OpenSpec change by creating the next artifact.

Core Features & Use Cases

  • Guides you through selecting or validating the next change artifact.
  • Generates the next artifact based on the current schema and status.
  • Ensures dependencies are respected and guardrails are enforced.

Quick Start

Use this skill to progress an OpenSpec change by generating 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 automate the next artifact creation in an OpenSpec change workflow?

To automate the next artifact creation in an OpenSpec change workflow, this skill generates the required artifact based on the current schema and status, ensuring dependencies are respected and guardrails are enforced.

What is the process for progressing an OpenSpec change through artifact dependencies?

Progressing an OpenSpec change follows an ordered artifact creation process that respects dependencies and guardrails, guiding you through selecting or validating the next change artifact to generate.

Do I need the OpenSpec CLI to continue generating change artifacts?

Yes, you need access to the OpenSpec CLI to continue generating change artifacts, as the automation requires the CLI to apply the ordered artifact creation process and enforce workflow guardrails.

How do I ensure OpenSpec guardrails are respected when creating a new artifact?

To ensure OpenSpec guardrails are respected when creating a new artifact, the skill validates the current schema and status before generating the subsequent artifact in the ordered sequence.

What's the best way to continue OpenSpec development after finishing the current artifact?

The best way to continue OpenSpec development after finishing an artifact is to use this skill to select or validate the next change artifact, generating it automatically based on the current status.