openspec-new-change

Creates a new OpenSpec change scaffold using the experimental artifact-driven workflow.

Updated Jul 31, 2026
One-click install
npx skills add https://github.com/germainlefebvre4/cvwonder-forms --skill openspec-new-change-germainlefebvre4
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-new-change
Source: https://github.com/germainlefebvre4/cvwonder-forms/tree/main/.gemini/skills/openspec-new-change
Command: npx skills add https://github.com/germainlefebvre4/cvwonder-forms --skill openspec-new-change-germainlefebvre4

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Starting a new feature, fix, or modification in an OpenSpec-managed project requires correctly scaffolding a change directory, choosing the right workflow schema, and understanding which artifact to create first. This Skill automates that setup so you begin every change with the correct structure and instructions. ## Core Features & Use Cases - Change Scaffolding: Runs openspec new change to create a properly named, kebab-case change directory in the resolved planning home. - Workflow Schema Selection: Uses the default schema automatically or applies a user-specified schema via --schema, with support for listing available workflows. - Artifact Guidance: Reports artifact status and retrieves the template and instructions for the first ready artifact without creating anything prematurely. - Use Case: You want to add user authentication to your project. Describe the goal, and the Skill derives the name add-user-auth, scaffolds the change, shows its 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 instructions.

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, then runs `openspec new change <name>` to scaffold the change. It then shows artifact status and the instructions for the first artifact without creating any content yet.

How do I use a different OpenSpec workflow schema?

Mention a specific schema name and the Skill passes `--schema <name>` to the new change command. If you ask what workflows exist, it runs `openspec schemas --json` so you can choose one.

Does openspec-new-change work with registered OpenSpec stores?

Yes. If you name a store, the Skill runs `openspec store list --json` to discover store ids and passes `--store <id>` on commands that read or write specs and changes. Without a store, commands act on the nearest local openspec root.

What happens if my change name is not kebab-case?

The Skill asks you for a valid kebab-case name before proceeding. If a change with that name already exists, it suggests continuing the existing change instead of creating a duplicate.

Does the Skill create artifacts automatically after scaffolding?

No. It stops after showing the first artifact's template and instructions, then waits for your direction. You can describe the change to have the artifact drafted or ask it to continue.