skills.rest
alexei-lexx
alexei-lexxCOMMUNITY
Explore all skills by this author →
GitHub

openspec-new-change

Scaffold new OpenSpec changes with kebab-case validation and artifact templates.

Updated Jun 4, 2025
Search Tags:#automation#cli#scaffold#openspec#change#artifact-workflow
One-click install
npx skills add https://github.com/alexei-lexx/budget --skill openspec-new-change-alexei-lexx
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-new-change
Source: https://github.com/alexei-lexx/budget/tree/main/.gemini/skills/openspec-new-change
Command: npx skills add https://github.com/alexei-lexx/budget --skill openspec-new-change-alexei-lexx

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Creating a new OpenSpec change often requires manual setup and remembering a sequence of steps. This skill automates starting a new change using the experimental artifact workflow, providing a structured path from naming to artifact sequencing.

Core Features & Use Cases

  • Guided change initiation: validates a kebab-case name, selects the default or explicit workflow schema, and scaffolds the change directory.
  • Artifact lifecycle guidance: reports artifact status and presents the first artifact template without creating artifacts.
  • Safe, repeatable process: enforces guardrails to prevent accidental changes and ensures consistent setup across teams.

Quick Start

Describe the change you want to create in kebab-case (e.g., add-user-auth) and I will generate the OpenSpec change scaffolding.

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 using the artifact workflow?▼

To scaffold an OpenSpec change, provide a kebab-case name describing the feature or fix. The automation validates the name, selects the default workflow schema, creates the change directory, and presents the first artifact template.

What is the experimental artifact workflow in OpenSpec?▼

The OpenSpec artifact workflow is a guided, multi-step process for creating changes. It enforces kebab-case naming, scaffolds directories, reports artifact status, and sequences templates to ensure consistent setup without generating artifacts automatically.

Does the OpenSpec change scaffolding process generate artifacts automatically?▼

No, the OpenSpec change scaffolding process does not generate artifacts. It creates the scaffold, reports current artifact status, and presents the first artifact template, stopping short of actual artifact generation to maintain safe guardrails.

How do I name a new change in OpenSpec?▼

You must name a new change in OpenSpec using kebab-case format, such as add-user-auth. The CLI automation validates this naming convention before proceeding with the scaffold creation and artifact sequencing.

Can I use a custom workflow schema instead of the default for OpenSpec changes?▼

Yes, OpenSpec change automation supports selecting an explicit workflow schema if provided. Otherwise, it defaults to the standard schema to scaffold the change directory and initiate the artifact workflow.

Related Skills

Explore More Software Engineering Skills→
moltbook-experimentsmoltbook-experiments
3

openspec-new-change

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

Official
Intermediate
tonysyutonysyu
2

openspec-ff-change

Automate OpenSpec change artifact creation with dependency ordering.

Community
Advanced
inflexa-aiinflexa-ai
29

openspec-propose

Generate proposal.md, design.md, and tasks.md via the openspec CLI.

Official
Advanced
SAPSAP
221

openspec-new-change

Create OpenSpec changes with kebab-case names and workflow schemas.

Official
Advanced