openspec-new-change

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

Updated Sep 16, 2026
One-click install
npx skills add https://github.com/JoeShi/coding-agent-usage-montior --skill openspec-new-change-joeshi
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-new-change
Source: https://github.com/JoeShi/coding-agent-usage-montior/tree/main/.kimi-code/skills/openspec-new-change
Command: npx skills add https://github.com/JoeShi/coding-agent-usage-montior --skill openspec-new-change-joeshi

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. This Skill walks through creating a new change scaffold and surfacing the first artifact template without skipping ahead. ## Core Features & Use Cases - Change Scaffolding: Runs openspec new change to create a kebab-case change directory with the default or user-specified workflow schema. - Status and Instructions: Shows artifact status via openspec status --json and retrieves the template for the first ready artifact with openspec instructions. - Store-Aware Operation: Supports registered OpenSpec stores by resolving store ids with openspec store list --json and passing --store <id> consistently. - Use Case: A developer says "I want to add OAuth login to our API" and the Skill derives the name add-oauth-login, scaffolds the change, and presents the proposal template ready for drafting. ## Quick Start Ask the assistant to start a new OpenSpec change for the feature or fix you want to build, and it will scaffold the change and show the first artifact template.

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?

Describe what you want to build, and the Skill derives a kebab-case name and runs `openspec new change <name>` to scaffold the change. It then shows artifact status and the instructions template for the first artifact without creating any content yet.

What naming format does OpenSpec require for changes?

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

Can I use a custom workflow schema with openspec new change?

Yes, pass `--schema <name>` when the user explicitly requests a specific workflow. Running `openspec schemas --json` lists available workflows; otherwise the default schema is used by omitting the flag.

Does this Skill create the change artifacts automatically?

No, it only scaffolds the change directory and displays the first artifact's template and instructions. Guardrails explicitly prevent creating artifacts or advancing beyond showing the first template until the user provides direction.

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

The Skill suggests continuing the existing change instead of creating a duplicate. It does not overwrite or re-scaffold an already-registered change name.