openspec-new-change

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

Updated Aug 7, 2026
One-click install
npx skills add https://github.com/javakishore-veleti/lifting-diary-app --skill openspec-new-change-javakishore-veleti
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-new-change
Source: https://github.com/javakishore-veleti/lifting-diary-app/tree/main/.qwen/skills/openspec-new-change
Command: npx skills add https://github.com/javakishore-veleti/lifting-diary-app --skill openspec-new-change-javakishore-veleti

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 workflow order. This Skill walks through the setup steps so a new change is scaffolded correctly without memorizing the openspec CLI. ## Core Features & Use Cases - Change Scaffolding: Runs openspec new change to create a structured change directory with the default or a user-specified workflow schema. - Store-Aware Operation: Detects registered OpenSpec stores via openspec store list --json and applies the --store flag consistently across all commands. - Artifact Guidance: Shows the current artifact status and retrieves the template and instructions for the first artifact without creating it prematurely. - Use Case: A developer wants to add user authentication to their app. 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 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?

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 first artifact template.

How do I use OpenSpec with a registered store?

Run `openspec store list --json` to discover registered store ids, then pass `--store <id>` on commands like new change, status, instructions, list, show, and validate. Keep the flag on all follow-up commands for that 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 Skill asks for a valid one before proceeding.

Can I use a different workflow schema in OpenSpec?

Yes, pass `--schema <name>` when creating the change if you explicitly want a non-default workflow. Run `openspec schemas --json` to list available workflows; otherwise the default schema is used automatically.

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

The Skill does not overwrite or duplicate the existing change. Instead it suggests continuing the existing change rather than creating a conflicting new one.