openspec-new-change

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

3|1|Updated Apr 29, 2026
One-click install
npx skills add https://github.com/firstsun-dev/skills --skill openspec-new-change-firstsun-dev
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-new-change
Source: https://github.com/firstsun-dev/skills/tree/main/plugins/spec-driven-development/skills/openspec-new-change
Command: npx skills add https://github.com/firstsun-dev/skills --skill openspec-new-change-firstsun-dev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Starting a spec-driven change often involves manual scaffolding, unclear naming conventions, and uncertainty about which artifact to write first. This Skill automates the creation of a new OpenSpec change directory and guides you through the first artifact step by step. ## Core Features & Use Cases - Change Scaffolding: Runs openspec new change to create a structured change directory with a kebab-case name derived from your description. - Schema Selection: Uses the default workflow by default, or a custom schema via --schema when you request a specific workflow. - Store Awareness: Discovers registered OpenSpec stores with openspec store list --json and applies --store <id> consistently across commands. - Use Case: You want to add user authentication to your project. Describe the goal, and the Skill creates the change add-user-auth, shows artifact status, and presents the template for the first artifact (e.g., the proposal) without writing any content yet. ## 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?▼

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

How do I use a custom workflow schema in OpenSpec?▼

Mention a specific schema name and the Skill passes `--schema <name>` to the new change command. Run `openspec schemas --json` to list available workflows if you are unsure which schema to use.

Does OpenSpec support multiple stores or repositories?▼

Yes, OpenSpec supports registered standalone stores. The Skill runs `openspec store list --json` to discover store ids and appends `--store <id>` to commands that read or write specs and changes for the rest of the workflow.

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

The Skill rejects invalid names and asks 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 this Skill write the proposal or other artifacts automatically?▼

No, the Skill stops after showing the first artifact's template and instructions. It explicitly waits for your direction before drafting any artifact content, following its guardrails.