openspec-new-change

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

Updated Sep 7, 2026
One-click install
npx skills add https://github.com/raphaelmans/spectralpointengineering --skill openspec-new-change-raphaelmans
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-new-change
Source: https://github.com/raphaelmans/spectralpointengineering/tree/main/.skillshare/skills/openspec-new-change
Command: npx skills add https://github.com/raphaelmans/spectralpointengineering --skill openspec-new-change-raphaelmans

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Starting a structured spec-driven change requires knowing the correct OpenSpec CLI commands, schema selection, and artifact sequencing, which is error-prone when done manually. ## Core Features & Use Cases - Change Scaffolding: Runs openspec new change to create a scaffolded change directory from a kebab-case name derived from the user's description. - Schema Selection: Uses the default workflow schema or a user-specified one via --schema, with discovery through openspec schemas --json. - Store Awareness: Detects registered OpenSpec stores with openspec store list --json and applies a sticky --store <id> flag to all scoped commands. - Use Case: A developer says "add user authentication"; the Skill derives add-user-auth, creates the change, shows artifact status, and presents the first artifact template without drafting content prematurely. ## 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 from the CLI?

Run `openspec new change "<name>"` with a kebab-case name to create a scaffolded change directory. Then use `openspec status --change "<name>" --json` to see artifact progress and `openspec instructions <artifact-id>` for the first artifact template.

How do I choose a different OpenSpec workflow schema?

Run `openspec schemas --json` to list available workflows, then pass `--schema <name>` when creating the change. If no schema is specified, the default workflow is used automatically.

What is an OpenSpec store and when do I need --store?

A store is a standalone OpenSpec repository registered on your machine. Run `openspec store list --json` to discover store ids, then append `--store <id>` to commands like new, status, instructions, and validate; without it, commands act on the nearest local openspec/ root.

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

The Skill asks for a valid kebab-case name before proceeding, since OpenSpec change names must follow that format. It derives a valid name from your description, such as converting "add user authentication" to add-user-auth.

Does this 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.