openspec-continue-change

Generate the next OpenSpec artifact from schema instructions and dependency order.

9|2|Updated Mar 12, 2026
One-click install
npx skills add https://github.com/fjpulidop/specrails-core --skill openspec-continue-change-fjpulidop
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-continue-change
Source: https://github.com/fjpulidop/specrails-core/tree/main/.claude/skills/openspec-continue-change
Command: npx skills add https://github.com/fjpulidop/specrails-core --skill openspec-continue-change-fjpulidop

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Continue a change by creating the next artifact within an OpenSpec workflow, enabling teams to advance work without losing context.

Core Features & Use Cases

  • Orchestrates artifact progression by reading the status of changes, selecting the next ready artifact, and generating its content according to the schema's guidance.
  • Maintains strict dependency ordering and guardrails to prevent skipping artifacts or overwriting dependencies.
  • Supports multiple schemas by applying the instruction templates and respecting constraints for creating artifacts.

Quick Start

Instruct the AI to continue the current OpenSpec change by generating the next artifact based on the latest status.

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 a change workflow by generating the next artifact?

To continue a change workflow, you instruct the AI to generate the next artifact based on the latest status. The tool identifies the next ready artifact, applies the schema instruction template, and writes the result to the designated output path.

What is artifact progression in an automated change management workflow?

Artifact progression in change management is the process of advancing work by reading completed artifacts for context, selecting the next ready artifact, and generating its content according to the schema's guidance without losing context.

Can I skip artifacts when creating content in an OpenSpec workflow?

No, you cannot skip artifacts in an OpenSpec workflow. The tool maintains strict dependency ordering and enforces guardrails to prevent skipping artifacts or overwriting dependencies during content generation.

Does the change management tool support multiple schemas for generating artifacts?

Yes, the change management tool supports multiple schemas by applying the instruction templates and respecting constraints for creating artifacts. It reads completed artifacts to maintain context across different schema configurations.

Why does my workflow status prevent overwriting dependencies during artifact generation?

Workflow status prevents overwriting dependencies because the tool enforces strict dependency ordering and guardrails. It reads the current status to ensure completed artifacts are protected while generating the next ready artifact.