openspec-new-change

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

Updated Feb 16, 2026
One-click install
npx skills add https://github.com/GQAdonis/artifact-refiner-skill --skill openspec-new-change-gqadonis
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-new-change
Source: https://github.com/GQAdonis/artifact-refiner-skill/tree/main/.kimi-code/skills/openspec-new-change
Command: npx skills add https://github.com/GQAdonis/artifact-refiner-skill --skill openspec-new-change-gqadonis

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 sequence. This Skill guides the AI through scaffolding a new change correctly, including store selection and kebab-case naming, without skipping required steps. ## 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: Discovers registered OpenSpec stores via openspec store list --json and applies a sticky --store <id> flag to all subsequent commands. - Artifact Guidance: Shows current artifact status and retrieves the template and instructions for the first artifact without prematurely creating content. - Use Case: A developer says "I want to add user authentication." The Skill derives the name add-user-auth, scaffolds the change, reports status, and presents the proposal template for the user to fill in next. ## 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 kebab-case change name or describe what you want to build, and the Skill derives a valid name. It then runs `openspec new change` to scaffold the change and shows the artifact status and first template.

How do I use a different OpenSpec workflow schema?▼

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

Does openspec-new-change work with registered stores?▼

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

What happens if my change name is not kebab-case?▼

The Skill rejects invalid names and asks for a valid kebab-case name before proceeding. If a change with that name already exists, it suggests continuing the existing change instead of creating a duplicate.

Does the Skill create the first artifact automatically?▼

No. It only scaffolds the change, shows status, and retrieves the first artifact's template and instructions. It then stops and waits for your direction before drafting any artifact content.