openspec-new-change

Scaffold a new OpenSpec change with a kebab-case name and workflow schema.

2|Updated Sep 23, 2025

Search Tags:#automation #guidance #cli #openspec #change-management #artifact-workflow #change-creation

Ready to run

npx skills add https://github.com/tonysyu/gqlxp --skill openspec-new-change-tonysyu

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: openspec-new-change
Source: https://github.com/tonysyu/gqlxp/tree/main/.claude/skills/openspec-new-change
Command: npx skills add https://github.com/tonysyu/gqlxp --skill openspec-new-change-tonysyu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Initiates a structured OpenSpec change using the experimental artifact workflow to guide feature work, fixes, or improvements, reducing ambiguity and setup time.

Core Features & Use Cases

Provides a repeatable process to create a new change, choose the workflow schema, and scaffold necessary files without performing any artifacts yet.
Supports default or explicit workflow schemas, status reporting, and generation of first-artifact instructions to kick off work.
Use Case: A developer wants to start a new feature using OpenSpec's artifact-driven workflow and needs a clear, repeatable setup.

Quick Start

Run openspec-new-change to begin a new OpenSpec change, then follow the prompts to name the change and choose the workflow.

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 with a structured workflow?▼

To start an OpenSpec change, use a guided artifact workflow that prompts for a kebab-case change name, scaffolds the directory, and reports the initial status without creating any artifacts yet.

What is the artifact workflow in OpenSpec change management?▼

The artifact workflow is a repeatable setup process for feature work or fixes that scaffolds the change directory and surfaces first-artifact instructions, ensuring structured initiation without immediately generating artifacts.

Can I specify a custom workflow schema when creating an OpenSpec change?▼

Yes, you can specify an explicit workflow schema when creating an OpenSpec change, or rely on the default schema to scaffold the necessary files and guide the setup process.

Do I need to provide a specific naming format for OpenSpec change creation?▼

Yes, OpenSpec change creation requires a kebab-case change name to ensure consistent directory scaffolding and proper artifact workflow initialization across engineering teams.

What is the best way to guide a development team through initiating feature work in OpenSpec?▼

The best way is using the OpenSpec artifact workflow, which reduces setup ambiguity by guiding teams through naming, schema selection, and directory scaffolding to standardize feature initiation.

Why does the OpenSpec change setup not create artifacts immediately?▼

The setup does not create artifacts immediately because it focuses on scaffolding the change directory and providing first-artifact instructions, allowing teams to review the status before proceeding.