skills.rest
BlackBeltTechnology
BlackBeltTechnologyOFFICIAL
Explore all skills by this author →
WebsiteGitHub

openspec-continue-change

Create the next OpenSpec artifact in a sequence using the OpenSpec CLI.

Updated May 5, 2022
Search Tags:#development workflow#cli#change management#openspec#artifact generation#schema driven
One-click install
npx skills add https://github.com/BlackBeltTechnology/judo-runtime-core --skill openspec-continue-change-blackbelttechnology
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-continue-change
Source: https://github.com/BlackBeltTechnology/judo-runtime-core/tree/main/.claude/skills/openspec-continue-change
Command: npx skills add https://github.com/BlackBeltTechnology/judo-runtime-core --skill openspec-continue-change-blackbelttechnology

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 creating the next required artifact in a defined workflow.

Core Features & Use Cases

  • Progress Workflow: Automatically determines and creates the next artifact needed for an OpenSpec change.
  • Contextual Awareness: Prompts the user for clarification if multiple changes are available or if the current change's status is unclear.
  • Artifact Generation: Creates specific artifact files (like proposals, specs, designs, or tasks) based on the workflow schema and instructions.
  • Use Case: After creating a proposal for a new feature, you can 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 development workflow and create the next artifact?▼

To continue an OpenSpec development workflow, this Skill programmatically determines and creates the next required artifact in your change sequence, such as a proposal, specification, design, or task file.

How does schema-driven artifact generation work for spec-driven changes?▼

Schema-driven artifact generation works by retrieving instructions for your current change status and creating the next specific file, like a specification, based on the capabilities outlined in your previous proposal.

Do I need the OpenSpec CLI to generate proposals and specifications?▼

Yes, you need the OpenSpec CLI installed because this Skill relies on it to perform status checks and retrieve the necessary artifact instructions for your current change.

What happens if I have multiple OpenSpec changes available in my project?▼

If multiple OpenSpec changes are available or the current change status is unclear, the Skill will prompt you for clarification to ensure it generates the correct artifact for the right workflow.

Can I automatically generate a specification file after creating a feature proposal?▼

Yes, you can automatically generate a specification file after creating a proposal; the Skill seamlessly progresses your workflow by creating the corresponding spec based on your outlined capabilities.

Related Skills

Explore More Software Engineering Skills→
sachinnair90sachinnair90

openspec-continue-change

Create the next required OpenSpec artifact based on current change status.

Community
Advanced
crozzbitecrozzbite

openspec-verify-change

Validate change implementations against openspec delta specifications, tasks, and design context.

Community
Advanced
jaxxstormjaxxstorm
4

openspec-continue-change

Create the next OpenSpec change artifact via the openspec CLI.

Community
Advanced
linaproailinaproai
147

openspec-propose

Generate proposal, design, and task artifacts via the openspec CLI.

Official
Advanced