openspec-new-change

Automate OpenSpec change creation with an artifact-driven workflow.

2|2|Updated Sep 20, 2023
One-click install
npx skills add https://github.com/zabiny/klabis --skill openspec-new-change-zabiny
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-new-change
Source: https://github.com/zabiny/klabis/tree/main/.opencode/skills/openspec-new-change
Command: npx skills add https://github.com/zabiny/klabis --skill openspec-new-change-zabiny

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Creating OpenSpec changes is often manual, error-prone, and tedious. This skill provides a structured, artifact-driven workflow to scaffold and manage new changes, ensuring consistency and repeatable processes.

Core Features & Use Cases

  • Automates the initial change setup in OpenSpec using the experimental artifact workflow.
  • Guides through status checks, schema selection, and first artifact instructions.
  • Useful for product teams and developers who need repeatable change processes.

Quick Start

Provide a kebab-case change name and a short description to start the new OpenSpec change workflow.

Frequently Asked Questions about openspec-new-change

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate scaffolding a new OpenSpec change?

Automate scaffolding a new OpenSpec change by providing a kebab-case change name and a short description to initialize the artifact-driven workflow, which then guides status checks and schema selection.

What is the artifact-driven workflow for OpenSpec change management?

The artifact-driven workflow for OpenSpec change management is a structured process that guides artifact creation sequentially, enforcing defined steps and preventing automatic generation until user confirmation to ensure repeatable processes.

How do I prevent automatic artifact generation when creating an OpenSpec change?

Prevent automatic artifact generation during OpenSpec change creation by requiring explicit user confirmation; the workflow pauses scaffolding and returns a summary of progress and next actions before generating the first artifact.

Do I need to format my OpenSpec change name in kebab-case?

Yes, you need to format your OpenSpec change name in kebab-case to initiate the workflow, as the automation requires this specific syntax to properly scaffold and manage the new change artifacts.

What's the best way to manage OpenSpec change workflows for product teams?

The best way to manage OpenSpec change workflows for product teams is using an automated scaffolding process that enforces consistent, repeatable steps from schema selection through artifact creation, eliminating manual setup errors.

Can I select a default workflow schema when scaffolding an OpenSpec change?

Yes, you can select a default workflow schema when scaffolding an OpenSpec change; the automation accepts a schema request during the initial setup and guides subsequent artifact creation accordingly.