openspec-continue-change

Continue an OpenSpec change by creating the next workflow artifact.

3|Updated Jan 27, 2026
One-click install
npx skills add https://github.com/Agentic-Engineering-Agency/specsafe --skill openspec-continue-change-agentic-engineering-agency
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-continue-change
Source: https://github.com/Agentic-Engineering-Agency/specsafe/tree/main/.opencode/skills/openspec-continue-change
Command: npx skills add https://github.com/Agentic-Engineering-Agency/specsafe --skill openspec-continue-change-agentic-engineering-agency

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill helps users continue their work on an OpenSpec change by creating the next required artifact in a defined workflow.

Core Features & Use Cases

  • Workflow Progression: Automatically determines and creates the next artifact (e.g., proposal, spec, test, code) based on the current state of an OpenSpec change.
  • Contextual Awareness: Infers the change to work on from conversation or prompts the user for selection if ambiguous.
  • Use Case: After creating a proposal for a new feature, you can use this Skill to automatically generate the detailed specification file for that feature.

Quick Start

Use the openspec continue change skill to create the next artifact for the 'user-authentication' change.

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 spec-driven workflow and generate the next artifact?

To continue a spec-driven workflow, the Skill executes CLI commands to check change status and automatically generates the next required artifact, such as a proposal or specification, based on predefined schema templates.

How does artifact generation work in a TDD development workflow?

Artifact generation in a TDD workflow follows sequential schema-specific templates and rules to create tests and code, ensuring sequential progress and providing status updates as each artifact is generated.

Can I use this to automatically create a specification file after finishing a feature proposal?

Yes, after creating a proposal for a new feature, this Skill automatically determines the current state of the OpenSpec change and generates the detailed specification file as the next workflow step.

What is the best way to manage sequential progress when creating OpenSpec changes?

The best way to manage sequential progress is by using this Skill to infer the active change from conversation context or prompt for selection, then automatically creating the next artifact in the defined workflow.

Does this workflow support both spec-driven and TDD schemas for artifact creation?

Yes, the workflow supports various schemas including spec-driven and TDD, executing CLI commands to list changes, check status, and generate instructions for schema-specific artifact creation.

Why does the workflow prompt me to select a change before generating instructions?

The workflow prompts for change selection when the target change is ambiguous, ensuring it correctly infers the context before executing CLI commands to generate the next artifact instructions.