openspec-new-change

Scaffold a new OpenSpec change with a kebab-case name and optional schema.

Updated Nov 26, 2025
One-click install
npx skills add https://github.com/hmj1026/docker_run --skill openspec-new-change-hmj1026
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-new-change
Source: https://github.com/hmj1026/docker_run/tree/main/.gemini/skills/openspec-new-change
Command: npx skills add https://github.com/hmj1026/docker_run --skill openspec-new-change-hmj1026

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Start a new change using the experimental artifact-driven approach. This workflow guides users to define a kebab-case change name, determine the default or requested workflow, and scaffold a structured OpenSpec change without manual setup.

Core Features & Use Cases

  • Input-driven scaffolding: Accepts a change name or description to derive a kebab-case identifier and create a dedicated change directory.
  • Workflow orchestration: Determines the workflow schema (default unless specified) and uses a guided sequence to create artifacts and track progress.
  • Status & instructions: Provides steps to check artifact readiness and fetch first artifact instructions, pausing for user direction before generating artifacts.
  • Guardrails: Prevents premature artifact creation and requires explicit user input to proceed to the next artifact.

Quick Start

Run a new change scaffold with openspec new change "<name>" and then follow the on-screen prompts to define the change and view the first artifact instructions.

Frequently Asked Questions about openspec-new-change

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

FAQPage Schema
How do I start a new OpenSpec change with a structured workflow?

To start a new OpenSpec change, run the scaffolding command with a kebab-case change name or description. This creates a dedicated directory and applies an artifact-driven workflow, pausing to provide status updates and first-artifact instructions before proceeding.

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

The artifact-driven workflow is a structured, repeatable process for OpenSpec changes that uses a defined sequence of artifacts. It guides feature creation by tracking progress and requiring explicit user input before generating the next artifact, preventing premature creation.

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

Yes, you can select an optional workflow schema during OpenSpec change scaffolding. If no specific schema is requested, the system automatically applies a default guided sequence to structure your artifacts and track progress.

How do I scaffold a kebab-case change directory for new features or fixes?

Provide a change name or description to the scaffolding tool, which parses the input into a kebab-case identifier. This automatically creates a structured OpenSpec change directory for your new feature, fix, or modification without manual setup.

Why does the OpenSpec change workflow pause before generating artifacts?

The OpenSpec change workflow pauses to enforce guardrails that prevent premature artifact creation. It provides status updates and first-artifact instructions, requiring explicit user direction before proceeding to generate the next artifact in the sequence.