openspec-continue-change

Generate the next OpenSpec change artifact from current status and templates.

1|Updated Apr 4, 2026
One-click install
npx skills add https://github.com/garethbaumgart/mental-metal --skill openspec-continue-change-garethbaumgart
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-continue-change
Source: https://github.com/garethbaumgart/mental-metal/tree/main/.claude/skills/openspec-continue-change
Command: npx skills add https://github.com/garethbaumgart/mental-metal --skill openspec-continue-change-garethbaumgart

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This feature helps teams keep OpenSpec changes moving by automatically creating the next artifact, reducing context switching and manual drift.

Core Features & Use Cases

  • Check the current change status in OpenSpec and determine what comes next.
  • Generate the next artifact using the project’s templates and required structure while honoring dependencies.
  • Enforce proper sequencing and guardrails, prompting for clarification when ambiguity exists.
  • Read completed artifacts to provide context for the new artifact and maintain traceability.

Quick Start

Ask me to continue the change on your OpenSpec workflow and I will 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 automate creating the next artifact in an OpenSpec change workflow?

Automating OpenSpec change continuation involves checking the current change status, reading dependencies, and generating the next artifact using template-driven output with strict sequencing and guardrails.

What is the process for continuing an OpenSpec change from the CLI?

The OpenSpec change continuation process uses CLI-based artifact generation to verify status, read completed artifacts for context, ensure proper sequencing, and output the next required artifact while prompting for clarification if ambiguity exists.

How does artifact sequencing and status verification work in OpenSpec change management?

Artifact sequencing in OpenSpec change management works by checking the current change status, enforcing proper sequencing guardrails, and reading completed artifacts to provide context and maintain traceability for the newly generated artifact.

Can I use CLI automation to generate OpenSpec artifacts while honoring template dependencies?

Yes, CLI automation generates OpenSpec artifacts by reading project dependencies, applying template-driven output structures, and enforcing strict sequencing guardrails to ensure proper artifact generation without manual drift.

Why does my OpenSpec change workflow prompt for clarification during artifact generation?

OpenSpec change workflows prompt for clarification during artifact generation when ambiguity exists in the change status or dependencies, acting as a guardrail to ensure proper sequencing and template-driven output accuracy.

What are the limitations of automating OpenSpec artifact generation via CLI?

Automating OpenSpec artifact generation via CLI requires strict sequencing and dependency reading to function properly, meaning it cannot generate artifacts out of order and will prompt for clarification when ambiguity exists in the change status.