openspec-new-change

Scaffolds a new OpenSpec change directory using the artifact-driven workflow.

4|Updated May 13, 2026
One-click install
npx skills add https://github.com/RuixeWolf/modbus-simulator --skill openspec-new-change-ruixewolf
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-new-change
Source: https://github.com/RuixeWolf/modbus-simulator/tree/main/.opencode/skills/openspec-new-change
Command: npx skills add https://github.com/RuixeWolf/modbus-simulator --skill openspec-new-change-ruixewolf

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 guides the AI through creating a properly scaffolded change with the experimental artifact workflow, avoiding manual setup errors. ## Core Features & Use Cases - Change Scaffolding: Runs openspec new change to create a structured change directory with the correct schema. - Store-Aware Operation: Discovers registered OpenSpec stores via openspec store list --json and applies --store <id> consistently across commands. - Artifact Guidance: Retrieves status and instructions for the first artifact (e.g., proposal) so the user knows exactly what to write next. - Use Case: A developer wants to add user authentication to their project. The Skill derives the kebab-case name add-user-auth, scaffolds the change, and presents the proposal template ready for drafting. ## Quick Start Ask the AI 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 the change directory. Then use `openspec status --change "<name>" --json` to see artifact progress and `openspec instructions <artifact-id>` to get the template for the first artifact.

How do I use OpenSpec with a registered store?▼

Run `openspec store list --json` to discover registered store ids, then append `--store <id>` to commands that read or write specs and changes, such as new change, status, instructions, show, and validate. Keep the flag on all follow-up commands in the workflow.

What naming format does OpenSpec require for changes?▼

Change names must be kebab-case, such as `add-user-auth` derived from a description like "add user authentication". If the name is invalid, the workflow asks for a valid name before proceeding.

Can I use a different workflow schema in OpenSpec?▼

Yes, pass `--schema <name>` when creating the change, but only if you explicitly need a non-default workflow. Run `openspec schemas --json` to list available workflows before choosing one.

What happens if an OpenSpec change already exists?▼

If a change with the same name already exists, the workflow suggests continuing that existing change instead of creating a duplicate. Use the status command to check its current artifact progress.