skills.rest
durandom
durandomCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

openspec-new-change

Scaffold an OpenSpec change workflow with kebab-case input normalization.

1|Updated Jan 21, 2026
Search Tags:#scaffold#kebab-case#openspec#project-planning#change-management#artifact-workflow
One-click install
npx skills add https://github.com/durandom/layton --skill openspec-new-change-durandom
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-new-change
Source: https://github.com/durandom/layton/tree/main/.claude/skills/openspec-new-change
Command: npx skills add https://github.com/durandom/layton --skill openspec-new-change-durandom

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides a structured, repeatable way to initiate a new OpenSpec change by outlining inputs, the chosen workflow, and artifact sequencing, reducing ambiguity and setup time.

Core Features & Use Cases

  • Guided name capture and kebab-case normalization for validation.
  • Default workflow selection and optional schema application to align with project conventions.
  • Artifact sequencing preview and non-destructive guidance before any file generation.

Quick Start

Ask the user for a kebab-case change name or a description of what to build, and I will generate the initial scaffold plan.

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 workflow for project planning?▼

OpenSpec change management initiates a structured workflow by capturing your input, normalizing it to kebab-case, and generating a non-destructive first-artifact scaffold to reduce ambiguity and setup time.

What is the default naming convention for OpenSpec artifact workflows?▼

OpenSpec artifact workflows enforce kebab-case normalization for change names to ensure consistent validation. This standardizes the scaffolding process and aligns generated artifacts with project conventions.

How do I generate a first-artifact plan using OpenSpec change management?▼

Provide a kebab-case change name or build description to generate an OpenSpec first-artifact plan. The workflow applies the default schema, sequences the artifacts, and presents a non-destructive template preview before file generation.

Can I apply a custom workflow schema to OpenSpec project planning changes?▼

You can apply an optional custom schema to align OpenSpec changes with project conventions. The workflow defaults to a standard process but accepts specified schemas to customize artifact sequencing and scaffolding.

Does OpenSpec scaffolding modify existing files when previewing artifact templates?▼

No, OpenSpec scaffolding is non-destructive. It previews the first-artifact template before generating any files, ensuring your existing project structure remains untouched until the workflow is explicitly approved.

When do I need an artifact-driven process for change management?▼

An artifact-driven process is needed for project planning tasks requiring repeatable workflows. OpenSpec change management reduces ambiguity by outlining inputs, applying schemas, and sequencing artifacts before generation.

Related Skills

Explore More Software Engineering Skills→
rafazafarrafazafar

openspec-new-change

Creates a new OpenSpec change scaffold with a kebab-case name and validates it.

Community
Intermediate
wzyxdwllwzyxdwll
14

openspec-new-change

Scaffold structured OpenSpec changes with artifact-driven workflows and validation.

Community
Intermediate
ncaqncaq
3

file-naming

The final result is a function of the initial conditions and the decisions made along the way.

Community
Intermediate
dentedgem9846-clawdentedgem9846-claw

openspec-new-change

Scaffold a new OpenSpec change and return the first artifact template.

Community
Intermediate