openspec-new-change

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

1|Updated Jun 30, 2026
One-click install
npx skills add https://github.com/trutoman/Conjuros --skill openspec-new-change-trutoman
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-new-change
Source: https://github.com/trutoman/Conjuros/tree/main/.opencode/skills/openspec-new-change
Command: npx skills add https://github.com/trutoman/Conjuros --skill openspec-new-change-trutoman

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Starting a structured spec-driven change requires knowing the OpenSpec CLI commands, schema selection, and artifact workflow order. This Skill walks through creating a new change scaffold and surfacing the first artifact's instructions without skipping steps. ## Core Features & Use Cases - Change Scaffolding: Runs openspec new change with a kebab-case name derived from the user's description, optionally with a custom workflow schema. - Status and Instruction Retrieval: Uses openspec status and openspec instructions to show artifact progress and the template for the first artifact. - Store-Aware Operation: Detects named OpenSpec stores via openspec store list --json and passes --store <id> to relevant commands. - Use Case: A developer wants to add user authentication with a spec-driven workflow; the Skill creates the add-user-auth change, shows 0/N artifact status, and presents the proposal template ready to draft. ## Quick Start Ask the assistant to start a new OpenSpec change for the feature 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` to get the first artifact template.

How do I choose a workflow schema in OpenSpec?

Omit the `--schema` flag to use the default workflow. If you need a different schema, run `openspec schemas --json` to list available workflows, then pass `--schema <name>` when creating the change.

What naming format does OpenSpec require for changes?

Change names must be kebab-case, such as `add-user-auth`. If the provided name is invalid, the Skill asks for a valid name before creating the change directory.

Can I use OpenSpec with a registered store instead of a local repo?

Yes. Run `openspec store list --json` to discover registered store ids, then pass `--store <id>` to commands like `new change`, `status`, `instructions`, `show`, and `validate`. Without a store, commands act on the nearest local `openspec/` root.

What happens if an OpenSpec change with that name already exists?

The Skill does not overwrite the existing change. It suggests continuing the existing change instead of creating a duplicate scaffold.