openspec-new-change

Scaffolds a new OpenSpec change directory and displays the first artifact instructions.

3|1|Updated May 29, 2026

Search Tags:#workflow #cli #spec-driven development #openspec #proposal #artifact #change scaffolding

One-click install

npx skills add https://github.com/mambo-wang/CodingHub --skill openspec-new-change-mambo-wang

Or copy as Structured Prompt for Agent▼

Please help me install this Agent Skill.
Skill: openspec-new-change
Source: https://github.com/mambo-wang/CodingHub/tree/main/.qoder/skills/openspec-new-change
Command: npx skills add https://github.com/mambo-wang/CodingHub --skill openspec-new-change-mambo-wang

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Starting a structured spec-driven change requires knowing the OpenSpec CLI commands, schema selection, and artifact workflow order, which is easy to get wrong manually. ## Core Features & Use Cases - Change Scaffolding: Runs `openspec new change` to create a properly structured change directory with a kebab-case name. - Workflow Schema Selection: Uses the default schema or a user-specified one via `--schema`, with support for listing available workflows. - Artifact Guidance: Shows change status via `openspec status --json` and retrieves the template for the first ready artifact without creating it prematurely. - Use Case: A developer wants to add user authentication to their project using spec-driven development; this Skill creates the change scaffold and presents the proposal template so drafting can begin immediately. ## Quick Start Ask the assistant to start a new OpenSpec change for the feature you want to build, for example by saying "start a new change to add user authentication".

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?▼

Run `openspec new change "<name>"` with a kebab-case name to scaffold the change directory. Then use `openspec status --change "<name>" --json` to see artifact paths and next steps.

How do I choose a different OpenSpec workflow schema?▼

Pass `--schema <name>` to the new change command to use a non-default workflow. Run `openspec schemas --json` to list available workflows before choosing one.

What naming format does OpenSpec require for changes?▼

Change names must be kebab-case, such as `add-user-auth`. If the provided name is invalid, the Skill asks for a valid name before proceeding.

Does this Skill create the change artifacts automatically?▼

No. It only scaffolds the change directory and displays the template and instructions for the first ready artifact, then stops and waits for user direction before drafting anything.

What happens if a change with the same name already exists?▼

The Skill does not overwrite it. It suggests continuing the existing change instead of creating a duplicate.