openspec-new-change

Scaffold an OpenSpec change workspace and display first artifact instructions.

Updated Mar 31, 2026
One-click install
npx skills add https://github.com/cenmiao/openspec-pro --skill openspec-new-change-cenmiao
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-new-change
Source: https://github.com/cenmiao/openspec-pro/tree/main/.claude/skills/openspec-new-change
Command: npx skills add https://github.com/cenmiao/openspec-pro --skill openspec-new-change-cenmiao

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill guides users through starting a new OpenSpec change by scaffolding the change directory, showing artifact status, and providing the first artifact template without creating any artifacts, removing uncertainty about initial setup and next steps.

Core Features & Use Cases

  • Guided Scaffolding: Creates a change scaffold using the openspec CLI and enforces naming validation (kebab-case).
  • Workflow Selection & Status: Selects or defaults a workflow schema, shows artifact readiness via openspec status, and retrieves the first artifact's instructions.
  • Safe First-Step Output: Presents the template and context for the first artifact but does not create or advance artifacts.
  • Use Case: A developer or spec author who wants to start a feature or fix can get a ready-to-edit artifact template and an overview of required artifacts before making any changes.

Quick Start

Tell me the change name in kebab-case or describe what you want to build and I will scaffold the change, show the artifact status, and display 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 scaffold a new OpenSpec change workspace?

Scaffolding an OpenSpec change requires the openspec CLI; you provide a kebab-case name or descriptive input to generate the change directory and view the first artifact template without creating any artifacts.

What is an artifact-driven workflow for change management?

An artifact-driven workflow structures feature or fix development around predefined artifact templates, showing artifact readiness status so spec authors follow a clear, sequential editing process before making changes.

Do I need the openspec CLI installed to start a new change?

Yes, the openspec CLI is required to scaffold a new change, enforce kebab-case naming validation, select workflow schemas, and retrieve the first artifact's instructions for the template.

How do I get the first artifact template without creating artifacts?

The scaffolding process runs openspec status to check artifact readiness and retrieves the first ready artifact's instructions, presenting the template context safely without actually creating or advancing artifacts.

Can I use a descriptive sentence instead of kebab-case to name my change?

Yes, you can describe what you want to build instead of providing a strict kebab-case name, and the scaffolder will derive a valid kebab-case name from your descriptive input automatically.

What are the limitations of scaffolding a new OpenSpec change?

The scaffolding output only displays instructions for the first ready artifact template and does not create, advance, or manage subsequent artifacts, requiring manual progression through the workflow.