skills.rest
guillaumejay
guillaumejayCOMMUNITY
Explore all skills by this author →
GitHub

openspec-new-change

Scaffold an OpenSpec change with a kebab-case name and default workflow.

Updated Jan 30, 2026
Search Tags:#cli#scaffold#kebab-case#openspec#change-management#artifact-workflow
One-click install
npx skills add https://github.com/guillaumejay/FileIndexer --skill openspec-new-change-guillaumejay
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-new-change
Source: https://github.com/guillaumejay/FileIndexer/tree/main/.gemini/skills/openspec-new-change
Command: npx skills add https://github.com/guillaumejay/FileIndexer --skill openspec-new-change-guillaumejay

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Streamline starting a new OpenSpec change by applying a structured, artifact-driven workflow that standardizes scaffolding and guidance for feature work or bug fixes.

Core Features & Use Cases

  • Automates scaffolding a new OpenSpec change with a kebab-case name.
  • Guides selection of a default or custom workflow and surfaces the first artifact instructions.
  • Provides a built-in guardrail flow to validate input and present status without creating artifacts.

Quick Start

Run openspec new change "<name>" to scaffold the change using the default 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 scaffold a new OpenSpec change with an artifact workflow?▼

Scaffolding a new OpenSpec change requires running the openspec new change command with a kebab-case name. This initiates the artifact workflow, automatically applying a structured process to standardize guidance for feature work or bug fixes.

What is the artifact workflow used for in OpenSpec change management?▼

The artifact workflow in OpenSpec change management standardizes how changes are started by providing structured, step-by-step guidance. It scaffolds the change with a kebab-case name and surfaces the first artifact instructions without creating artifacts.

Do I need the OpenSpec CLI to start a new change with artifact scaffolding?▼

Yes, the OpenSpec CLI is required to start a new change with artifact scaffolding. The CLI executes the command to create the kebab-case named change and surfaces the default workflow's first artifact instructions.

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

Yes, you can choose between the default workflow or a custom workflow when creating an OpenSpec change. The process guides you through workflow selection and surfaces the first artifact instructions for the chosen path.

Does creating a new OpenSpec change automatically generate the initial artifacts?▼

Creating a new OpenSpec change does not automatically generate artifacts. A built-in guardrail flow validates the input and surfaces the status and first artifact instructions, ensuring artifacts are only created when explicitly requested.

Related Skills

Explore More Software Engineering Skills→
pabloimrik17pabloimrik17

openspec-continue-change

Create the next required OpenSpec artifact and advance change workflow via CLI.

Community
Intermediate
cynkracynkra
1

openspec-continue-change

Continue an OpenSpec change by generating the next schema-ordered artifact.

Official
Intermediate
moltbook-experimentsmoltbook-experiments
3

openspec-new-change

Bootstrap a new OpenSpec change with kebab-case naming and schema selection.

Official
Intermediate
sgiathsgiath
4

openspec-new-change

Scaffold a new OpenSpec change directory with an artifact-driven workflow.

Community
Intermediate