openspec-new-change

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

Updated Apr 6, 2026
One-click install
npx skills add https://github.com/capella-hotel-group/capella-hotel-group-poc --skill openspec-new-change-capella-hotel-group
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-new-change
Source: https://github.com/capella-hotel-group/capella-hotel-group-poc/tree/main/.github/skills/openspec-new-change
Command: npx skills add https://github.com/capella-hotel-group/capella-hotel-group-poc --skill openspec-new-change-capella-hotel-group

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Starting a spec-driven change requires knowing the correct OpenSpec CLI commands, schema selection, and artifact ordering. This Skill walks you through creating a properly scaffolded change directory so you never miss a setup step. ## Core Features & Use Cases - Guided Change Creation: Derives a kebab-case change name from your description and runs openspec new change with the correct schema flags. - Artifact Status Inspection: Runs openspec status to show which artifacts are ready and which dependencies remain. - First Artifact Instructions: Fetches the template and context for the first artifact (e.g., proposal) so you can start drafting immediately. - Use Case: You want to add user authentication to your app using a spec-driven workflow. Describe the feature, and this Skill scaffolds openspec/changes/add-user-auth/ and shows you the proposal template to begin. ## 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?▼

Run `openspec new change "<name>"` with a kebab-case name to scaffold a change directory under `openspec/changes/<name>/`. Then use `openspec status --change "<name>"` to see which artifacts are ready to create.

How do I choose a workflow schema in OpenSpec?▼

Omit the `--schema` flag to use the default schema, which fits most changes. Pass `--schema <name>` only when you need a specific workflow, and run `openspec schemas --json` to list available options.

What happens after creating an OpenSpec change directory?▼

The CLI scaffolds the change at `openspec/changes/<name>/` with the selected schema. You then check artifact status and run `openspec instructions <artifact-id> --change "<name>"` to get the template for the first ready artifact, such as the proposal.

What if my OpenSpec change name is invalid or already exists?▼

Change names must be kebab-case; invalid names should be corrected before running the command. If a change with that name already exists, continue working on the existing change instead of creating a duplicate.

Does this Skill create the change artifacts automatically?▼

No. It only scaffolds the change directory and displays the instructions and template for the first artifact. You then describe the change content so the artifact can be drafted in a follow-up step.