openspec-new-change

Scaffolds a new OpenSpec change and displays the first artifact instructions.

Updated Aug 5, 2026
One-click install
npx skills add https://github.com/JhonMA82/api-starter --skill openspec-new-change-jhonma82
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-new-change
Source: https://github.com/JhonMA82/api-starter/tree/main/.opencode/skills/openspec-new-change
Command: npx skills add https://github.com/JhonMA82/api-starter --skill openspec-new-change-jhonma82

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Starting a 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 template 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. - Store-aware execution: Discovers registered OpenSpec stores via openspec store list --json and applies --store <id> consistently across commands. - Artifact guidance: Shows change status as JSON and retrieves instructions for the first ready artifact, then stops for user direction. - Use Case: A developer says "add user authentication"; the Skill derives add-user-auth, creates the change, and presents the proposal template ready to draft. ## 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?▼

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 follows with status and instructions commands to show the first artifact template.

How do I use a different OpenSpec workflow schema?▼

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

Does this Skill work with OpenSpec stores?▼

Yes. If you name a store or the work lives in one, it runs `openspec store list --json` to find the store id and appends `--store <id>` to all commands that read or write specs and changes.

Does the Skill create the change artifacts automatically?▼

No. It only scaffolds the change directory and displays the first artifact's template and instructions. It explicitly stops and waits for your direction before drafting any artifact content.

What happens if the change name is invalid or already exists?▼

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