openspec-new-change

Create an OpenSpec change scaffold with kebab-case naming and schema selection.

Updated Jan 29, 2026
One-click install
npx skills add https://github.com/AdJIa/markdown-x --skill openspec-new-change-adjia
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-new-change
Source: https://github.com/AdJIa/markdown-x/tree/main/.cursor/skills/openspec-new-change
Command: npx skills add https://github.com/AdJIa/markdown-x --skill openspec-new-change-adjia

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

OpenSpec change initiation often requires careful setup to ensure changes are tracked and implemented consistently. This skill provides an automated, artifact-driven approach to start a new change, guiding users through naming, schema selection, and scaffold creation.

Core Features & Use Cases

  • Guided change creation: enforces kebab-case naming, default or explicit workflow schema, and scaffold generation.
  • Artifact-first workflow: shows status and instructions for the first artifact without creating anything yet.
  • Guardrails and prompts: ensures user intent is clarified before proceeding and offers interactive prompts to confirm details.
  • Use Case: A product team wants to start a feature or fix with a reproducible OpenSpec change, and they want a structured plan before implementation.

Quick Start

Run openspec new change with a kebab-case name and follow the prompts to view 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 create a new OpenSpec change using the CLI?

To create an OpenSpec change, run the openspec CLI with a kebab-case name. This guided workflow handles schema selection and scaffolding, then reports the artifact status and first template without creating artifacts.

What is an artifact-driven workflow for change management?

An artifact-driven workflow for change management structures feature work by scaffolding changes first. It displays the status and template of the first artifact before creation, ensuring a reproducible, structured plan before implementation.

Do I need the openspec CLI installed to scaffold changes?

Yes, you need the openspec CLI installed and accessible in your system path to scaffold changes. The CLI is required to execute the guided naming, schema selection, and artifact workflow generation.

Why does my OpenSpec change require a kebab-case name?

Your OpenSpec change requires a kebab-case name to ensure consistent tracking and organization of feature work. The guided workflow enforces this naming convention automatically during the scaffold creation process.

Does the openspec new change command create artifacts automatically?

No, the openspec new change command does not create artifacts automatically. It scaffolds the change structure and displays the first artifact template, allowing you to review the plan before any artifacts are actually generated.

What is the best way to start a feature fix with OpenSpec change management?

The best way to start a feature fix with OpenSpec change management is using an automated scaffold. It guides you through kebab-case naming and schema selection to establish a structured, reproducible plan before implementation.