openspec-new-change

Creates a new OpenSpec change scaffold using the artifact-driven workflow via the openspec CLI.

1|Updated Apr 9, 2026
One-click install
npx skills add https://github.com/CoderCoco-Studios/Hyveon --skill openspec-new-change-codercoco-studios
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-new-change
Source: https://github.com/CoderCoco-Studios/Hyveon/tree/main/.claude/skills/openspec-new-change
Command: npx skills add https://github.com/CoderCoco-Studios/Hyveon --skill openspec-new-change-codercoco-studios

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Starting a new feature or fix with OpenSpec requires knowing the correct CLI commands, schema selection, and artifact sequencing. This Skill walks through the structured setup of a new change so the scaffold, status, and first artifact template are created correctly without manual CLI guesswork. ## Core Features & Use Cases - Change Scaffolding: Runs openspec new change with a validated kebab-case name to create the change directory in the resolved planning home. - Workflow Schema Selection: Uses the default schema by default, or a user-specified schema via --schema, with discovery through openspec schemas --json. - Status and Instructions Retrieval: Reports artifact status via openspec status --json and fetches the template for the first ready artifact with openspec instructions. - Use Case: A developer says "I want to add user authentication." The Skill derives the name add-user-auth, scaffolds the change, shows 0/N artifact status, 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?

Provide a description of what you want to build, and the Skill derives a kebab-case name and runs `openspec new change <name>`. It then shows the artifact status and the template for the first artifact, such as the proposal.

How do I use a different OpenSpec workflow schema?

Mention a specific schema name and it is passed via `--schema <name>` to `openspec new change`. To browse available workflows, ask to show workflows, which runs `openspec schemas --json` so you can choose.

Does openspec new change require the openspec CLI?

Yes, the openspec CLI must be installed on the machine since all operations run through commands like `openspec new change`, `status`, and `instructions`. Without the CLI, the Skill cannot scaffold or inspect changes.

What happens if the change name already exists in OpenSpec?

If a change with the same name already exists, the Skill suggests continuing that existing change instead of creating a duplicate. Invalid names that are not kebab-case are rejected with a request for a valid name.

Does the Skill create the proposal or other artifacts automatically?

No, the Skill stops after displaying the first artifact's template and instructions. It explicitly does not create any artifacts, waiting for the user to describe the change so the artifact can be drafted next.