openspec-new-change

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

Updated Jun 25, 2026
One-click install
npx skills add https://github.com/ismaelsoilet/ismaelsoilet-landing --skill openspec-new-change-ismaelsoilet
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-new-change
Source: https://github.com/ismaelsoilet/ismaelsoilet-landing/tree/main/.cursor/skills/openspec-new-change
Command: npx skills add https://github.com/ismaelsoilet/ismaelsoilet-landing --skill openspec-new-change-ismaelsoilet

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Starting a structured spec-driven change requires knowing the correct OpenSpec CLI commands, schema selection, and artifact workflow order, which is error-prone when done manually. ## Core Features & Use Cases - Change Scaffolding: Creates a new kebab-case change directory via openspec new change with optional schema selection. - Artifact Status Inspection: Runs openspec status and openspec instructions to show the artifact sequence and the template for the first artifact. - Store-Aware Operation: Detects registered OpenSpec stores with openspec store list --json and passes --store <id> to commands that read or write specs. - Use Case: A developer wants to add user authentication using a spec-driven workflow; the Skill derives the name add-user-auth, scaffolds the change, and presents the proposal template for drafting. ## 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 OpenSpec 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 from the CLI?▼

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 progress and `openspec instructions <artifact-id>` to get the first artifact template.

What naming format does an OpenSpec change require?▼

Change names must be kebab-case, such as `add-user-auth`. If the provided name is not valid kebab-case, the workflow asks for a corrected name before creating the change directory.

How do I use a different OpenSpec workflow schema?▼

Pass `--schema <name>` to `openspec new change` when you need a non-default workflow. Run `openspec schemas --json` to list available schemas and choose one before scaffolding.

Does OpenSpec support multiple stores or repositories?▼

Yes. Run `openspec store list --json` to discover registered store ids, then pass `--store <id>` to commands that read or write specs and changes, such as status, instructions, show, and validate.

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

The workflow does not overwrite the existing change. Instead it suggests continuing the existing change, so you can resume its artifact sequence rather than creating a duplicate.