openspec-new-change

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

Updated Mar 17, 2026
One-click install
npx skills add https://github.com/beliciobcardoso/mcp-postgres --skill openspec-new-change-beliciobcardoso
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-new-change
Source: https://github.com/beliciobcardoso/mcp-postgres/tree/main/.qwen/skills/openspec-new-change
Command: npx skills add https://github.com/beliciobcardoso/mcp-postgres --skill openspec-new-change-beliciobcardoso

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 ordering. This Skill guides the AI through scaffolding a new change directory and surfacing the first artifact instructions without skipping steps. ## Core Features & Use Cases - Change Scaffolding: Runs openspec new change with a validated kebab-case name to create the change directory under openspec/changes/. - Workflow Schema Selection: Uses the default schema unless the user explicitly requests a different workflow via --schema. - Artifact Status & Instructions: Shows artifact readiness with openspec status and retrieves the template for the first ready artifact. - Use Case: A developer says "I want to add user authentication." The Skill derives the name add-user-auth, scaffolds the change, shows the artifact sequence, and presents the proposal template for drafting. ## Quick Start Ask the AI 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 a change directory under `openspec/changes/`. Then use `openspec status --change "<name>"` to see which artifacts are ready to create.

How do I choose a workflow schema in OpenSpec?▼

The default schema is used when you omit the `--schema` flag. To pick a different workflow, run `openspec schemas --json` to list available schemas, then pass the chosen one with `--schema <name>` when creating the change.

What naming format does OpenSpec require for changes?▼

Change names must be in kebab-case, such as `add-user-auth`. If the provided name is not valid kebab-case, the Skill asks for a corrected name before creating the change.

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

The Skill does not overwrite the existing change. Instead, it suggests continuing the existing change rather than creating a duplicate scaffold.

Does the OpenSpec new change workflow create artifacts automatically?▼

No. The workflow only scaffolds the change directory and displays the template and instructions for the first ready artifact. It stops and waits for user direction before drafting any artifact content.