skills.rest
yuanhsunliu
yuanhsunliuCOMMUNITY
Explore all skills by this author →
GitHub

openspec-new-change

Scaffold OpenSpec changes with kebab-case naming and optional schema selection.

Updated Aug 27, 2026
Search Tags:#workflow#guidance#kebab-case#openspec#change-management#artifact-workflow
One-click install
npx skills add https://github.com/yuanhsunliu/dashboard-layout-editor-ui --skill openspec-new-change-yuanhsunliu
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-new-change
Source: https://github.com/yuanhsunliu/dashboard-layout-editor-ui/tree/main/.github/skills/openspec-new-change
Command: npx skills add https://github.com/yuanhsunliu/dashboard-layout-editor-ui --skill openspec-new-change-yuanhsunliu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Solves the problem of starting OpenSpec changes by automating a structured, artifact-driven setup.

Core Features & Use Cases

  • Guided change initiation: Creates a scaffold for a new OpenSpec change using a kebab-case name and optional schema, so your team starts from a consistent baseline.
  • Artifact sequencing: Outlines the recommended steps to determine the change name, select a workflow schema, scaffold the change, monitor status, and retrieve instructions for the first artifact.
  • Guardrails and clarity: Enforces naming conventions, clarifying questions, and non-destructive guidance to prevent premature artifact creation.

Quick Start

Describe the kebab-case change name and, if needed, the schema, and I will guide you through the next steps without creating artifacts.

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 structured change management workflow for a new feature request?▼

To start a structured change management workflow, provide a kebab-case change name and an optional schema to initiate a guided, artifact-driven setup process. This scaffolds the change baseline without creating artifacts prematurely.

What is an artifact-driven change workflow and when do I need it?▼

An artifact-driven change workflow uses a staged sequence of defined outputs to manage feature requests, bug fixes, or process improvements. You need it to ensure repeatable, consistent change initiation across your team.

How do I enforce kebab-case naming conventions for project changes?▼

To enforce kebab-case naming conventions, use a guided workflow that applies guardrails during change initiation. The workflow validates the name format and clarifies the requirements before scaffolding proceeds.

Can I select a specific workflow schema when initiating an OpenSpec change?▼

Yes, you can select a specific workflow schema when initiating an OpenSpec change. The guided setup allows optional schema selection to tailor the artifact sequence to your specific process requirements.

Does the change management setup process create artifacts automatically?▼

No, the change management setup process does not create artifacts automatically. It provides non-destructive guidance and outlines the steps to retrieve instructions for the first artifact, preventing premature artifact creation.

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
AdJIaAdJIa

openspec-continue-change

Create the next artifact in an OpenSpec change workflow.

Community
Advanced
jaxxstormjaxxstorm
4

openspec-continue-change

Create the next OpenSpec change artifact via the openspec CLI.

Community
Advanced
LippyyDevLippyyDev
1

openspec-new-change

Scaffold OpenSpec changes with naming conventions and artifact sequencing.

Community
Intermediate