skills.rest
rozx
rozxCOMMUNITY
Explore all skills by this author →
GitHub

openspec-new-change

Scaffold a new OpenSpec change directory with a ready-to-fill artifact template.

25|4|Updated Nov 13, 2025
Search Tags:#automation#workflow#devops#scaffolding#cli#openspec#change-management
One-click install
npx skills add https://github.com/rozx/Tsukuyomi --skill openspec-new-change-rozx
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-new-change
Source: https://github.com/rozx/Tsukuyomi/tree/main/.opencode/skills/openspec-new-change
Command: npx skills add https://github.com/rozx/Tsukuyomi --skill openspec-new-change-rozx

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

OpenSpec change setup often requires manual scaffolding and artifact planning. This Skill automates the initial creation with a structured, repeatable workflow powered by the experimental artifact tooling.

Core Features & Use Cases

  • Structured scaffold: creates a new OpenSpec change directory at openspec/changes/<name> with a ready-to-edit template.
  • Workflow-guided setup: enforces the default artifact-driven process and ensures the first artifact is prepared but not emitted automatically.
  • Safety and governance: enforces kebab-case naming, default schema selection, and visibility into artifact readiness to prevent misconfigurations.

Quick Start

Provide a kebab-case change name and I will scaffold the OpenSpec change using the default artifact 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 using an artifact-driven workflow?▼

To scaffold an OpenSpec change, provide a kebab-case name and the workflow creates a directory at openspec/changes/<name>. It prepares a ready-to-fill first artifact template while enforcing the default artifact-driven process without emitting artifacts automatically.

Do I need the openspec CLI to create new OpenSpec change scaffolds?▼

Yes, creating new OpenSpec change scaffolds requires the openspec CLI. The CLI powers the automated workflow that generates the structured directory and enforces naming conventions and default schema selection for your changes.

What is the default naming convention for OpenSpec change directories?▼

OpenSpec change directories require kebab-case naming. This governance ensures visibility into artifact readiness and prevents misconfigurations when scaffolding new features, fixes, or modifications in the openspec/changes/<name> path.

Does the OpenSpec scaffolding workflow automatically generate all change artifacts?▼

No, the OpenSpec scaffolding workflow does not create artifacts automatically. It preserves a ready-to-fill first artifact template, ensuring you manually populate the structured artifact content after the initial change directory is scaffolded.

When should I use an artifact-driven workflow for OpenSpec change management?▼

Use an artifact-driven workflow for OpenSpec change management when your team needs structured, repeatable scaffolding for new features or fixes. It enforces default schema selection and artifact readiness visibility to prevent misconfigurations during manual setup.

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
Rushtu99Rushtu99

openspec-new-change

Initialize an OpenSpec change workflow with schema selection and status checks.

Community
Intermediate
fjpulidopfjpulidop
9

openspec-new-change

Scaffold OpenSpec change directories and guide first artifact creation.

Community
Advanced
SiddharthChillaleSiddharthChillale

openspec-new-change

Scaffold OpenSpec changes with kebab-case names and first artifact templates.

Community
Intermediate