openspec-new-change

Scaffolds a new OpenSpec change and displays the first artifact template via the openspec CLI.

1|1|Updated Jan 25, 2026
One-click install
npx skills add https://github.com/phuchoang2603/nixos --skill openspec-new-change-phuchoang2603
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-new-change
Source: https://github.com/phuchoang2603/nixos/tree/main/home/base/cli/skills/openspec-new-change
Command: npx skills add https://github.com/phuchoang2603/nixos --skill openspec-new-change-phuchoang2603

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 workflow order, which is error-prone when done manually. ## Core Features & Use Cases - Change Scaffolding: Creates a new kebab-case change directory using openspec new change with optional schema selection. - Artifact Status Inspection: Runs openspec status and openspec instructions to show the artifact sequence and the template for the first ready artifact. - Store-Aware Operation: Discovers registered OpenSpec stores with openspec store list --json and applies a sticky --store <id> flag to all scoped commands. - Use Case: A developer wants to add user authentication to a project; the skill derives the name add-user-auth, scaffolds the change, and presents the proposal template without writing any artifacts. ## 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?▼

Provide a change name in kebab-case or describe what you want to build, and the skill runs `openspec new change <name>` to scaffold it. It then shows the artifact status and the template for the first ready artifact without creating any artifacts.

How do I use a different OpenSpec workflow schema?▼

Mention a specific schema name and the skill passes `--schema <name>` to `openspec new change`. If you ask what workflows exist, it runs `openspec schemas --json` so you can choose; otherwise the default schema is used.

Does this skill work with OpenSpec stores?▼

Yes. If you name a store, it runs `openspec store list --json` to discover registered store ids, then appends `--store <id>` to all commands that read or write specs and changes for the rest of the workflow.

What happens if the change name already exists?▼

The skill does not overwrite existing changes. If a change with that name already exists, it suggests continuing that change instead of creating a duplicate.

Does the skill create the change artifacts automatically?▼

No. The guardrails explicitly stop after showing the first artifact template and instructions. It waits for your direction before drafting or creating any artifacts.