openspec-new-change

Scaffold an OpenSpec change directory with a kebab-case name and workflow schema.

6|Updated Feb 13, 2021
One-click install
npx skills add https://github.com/dezkareid/dezkareid --skill openspec-new-change-dezkareid
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-new-change
Source: https://github.com/dezkareid/dezkareid/tree/main/design-system/design-tokens/.gemini/skills/openspec-new-change
Command: npx skills add https://github.com/dezkareid/dezkareid --skill openspec-new-change-dezkareid

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Start a new OpenSpec change using the experimental artifact-driven workflow to standardize how changes are proposed, tracked, and validated without prematurely creating artifacts.

Core Features & Use Cases

  • Provides a guided process to initialize an OpenSpec change with a scaffolded directory structure.
  • Derives a kebab-case change name from user input, optionally selects a workflow schema, and creates openspec/changes/<name>/ as the workspace.
  • Walks you through the first artifact step by step and presents instructions without performing any artifacts, enabling safe planning for feature work, bug fixes, or improvements.

Quick Start

Describe your change in kebab-case name and a brief description, and I will scaffold the change using the experimental artifact-driven 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 scaffold a new OpenSpec change directory for artifact-driven workflows?

To scaffold an OpenSpec change, this guided process derives a kebab-case change name from your input, optionally selects a workflow schema, and creates the openspec/changes/<name>/ directory structure without generating any artifacts prematurely.

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

The artifact-driven workflow is an experimental process that standardizes how changes are proposed, tracked, and validated. It sequences artifact creation step by step within a scaffolded directory to enable safe planning for feature work or bug fixes.

Does the OpenSpec change scaffolding process create proposal artifacts automatically?

No, the scaffolding process explicitly does not create artifacts. It establishes the workspace directory and provides first-artifact instructions, enforcing guardrails to ensure valid user input before you manually perform any artifact creation steps.

How do I start an OpenSpec change initiation for a bug fix or feature?

You start change initiation by providing a brief description of your bug fix or feature. The workflow derives a valid kebab-case name, selects a schema, scaffolds the workspace, and walks you through the first artifact instructions step by step.

What naming conventions are required for OpenSpec change management scaffolding?

OpenSpec change management requires a kebab-case naming convention for the change directory. The scaffolding process enforces guardrails to validate your input and ensure the derived name correctly structures the openspec/changes/<name>/ path.

When should I use an artifact-driven workflow instead of directly modifying OpenSpec specifications?

You should use the artifact-driven workflow when you need to standardize how changes are proposed and validated without premature artifact creation. It clarifies the artifact sequence and provides structured instructions, enabling safe planning before modifying specifications.