openspec-continue-change

Create the next OpenSpec workflow artifact using the OpenSpec CLI.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/AlexanderRadevich/SportowyHub_clientApp --skill openspec-continue-change-alexanderradevich
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-continue-change
Source: https://github.com/AlexanderRadevich/SportowyHub_clientApp/tree/main/.claude/skills/openspec-continue-change
Command: npx skills add https://github.com/AlexanderRadevich/SportowyHub_clientApp --skill openspec-continue-change-alexanderradevich

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill helps users continue working on their OpenSpec changes by guiding them through the creation of the next artifact in a defined workflow.

Core Features & Use Cases

  • Progress Workflow: Automatically determines and creates the next required artifact based on the current status of an OpenSpec change.
  • Guided Artifact Creation: Provides context, rules, and templates for creating artifacts like proposals, specs, designs, and tasks.
  • Use Case: After creating a proposal for a new feature, use this Skill to automatically generate the corresponding specification file based on the capabilities outlined in the proposal.

Quick Start

Use the openspec-continue-change skill to create the next artifact for your current 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 an OpenSpec change workflow and generate the next artifact?

To continue an OpenSpec change, this Skill programmatically checks the current status and creates the next artifact in the workflow. It uses the OpenSpec CLI to determine status and generate the appropriate file based on predefined schemas.

What is the spec-driven workflow for generating OpenSpec artifacts?

The spec-driven workflow is a predefined schema for OpenSpec changes that guides the creation of sequential artifacts. It includes generating proposals, specs, design documents, and tasks to ensure structured development and comprehensive artifact creation.

Do I need the OpenSpec CLI to generate specification files from a proposal?

Yes, you need the OpenSpec CLI installed to generate specification files. The Skill requires the CLI to perform status checks, retrieve creation instructions, and programmatically generate the required workflow artifacts.

How do I automatically create a specification file after writing an OpenSpec proposal?

You can automatically create a specification file by running this Skill after your proposal is complete. It evaluates the capabilities outlined in the proposal and applies guided templates and rules to generate the corresponding spec artifact.

Can I use this Skill to manage task creation for development workflows?

Yes, you can use this Skill for task creation within development workflows. It supports the spec-driven schema, which includes generating task artifacts to guide the implementation phase after proposals and specifications are finalized.

What are the limitations of using predefined schemas for OpenSpec artifact generation?

The limitation of predefined schemas is that artifact generation is restricted to specific workflows like spec-driven. You must follow the sequential proposal, specs, design, and tasks structure, which limits flexibility for non-standard development processes.