skills.rest
kunish
kunishCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

openspec-new-change

Scaffold OpenSpec changes with a guided artifact-driven workflow.

Updated Mar 4, 2026
Search Tags:#scaffolding#cli#openspec#development-workflow#change-management#project-automation
One-click install
npx skills add https://github.com/kunish/muon --skill openspec-new-change-kunish
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-new-change
Source: https://github.com/kunish/muon/tree/main/.github/skills/openspec-new-change
Command: npx skills add https://github.com/kunish/muon --skill openspec-new-change-kunish

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Plan and scaffold OpenSpec changes with a guided artifact-driven workflow.

Core Features & Use Cases

  • Structured setup for a new OpenSpec change at openspec/changes/<name> using the default schema.
  • Guided artifact sequencing: status checks, first-artifact instructions, and ready-state reporting.
  • Ideal for feature tweaks, bug fixes, or design changes within OpenSpec projects.

Quick Start

Provide a kebab-case change name to scaffold a new 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 for a feature request or bug fix?▼

To scaffold an OpenSpec change, provide a kebab-case change name. The workflow initializes the change directory at openspec/changes/<name> using the default schema and provides first-artifact instructions without creating artifacts automatically.

What is the artifact-driven workflow for OpenSpec change management?▼

The artifact-driven workflow for OpenSpec change management guides you through naming, schema selection, change creation, status checks, and first-artifact instructions. It sequences artifacts step-by-step and reports ready-states without auto-generating the actual artifacts.

Do I need to manually create artifacts when starting an OpenSpec change?▼

No, you do not manually create artifacts immediately. The scaffolding workflow provides a ready-to-use first-artifact template and instructions, leaving the actual artifact creation to you when the change status indicates readiness.

Can I use OpenSpec scaffolding for design updates and project automation?▼

Yes, OpenSpec scaffolding applies to feature tweaks, bug fixes, and design updates within OpenSpec projects. It automates the structured setup and status reporting for development-workflow change management.

What is the default schema for an OpenSpec change directory?▼

The default schema structures your OpenSpec change at openspec/changes/<name>. It initializes the change with a default artifact workflow, performing status checks and providing a first-artifact template to guide your project automation sequence.

Why does my OpenSpec change scaffold not include generated artifacts?▼

OpenSpec scaffolding intentionally avoids creating artifacts automatically to keep you in control of the artifact-driven workflow. It only initializes the change, reports status, and provides first-artifact instructions and templates for you to populate.

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
wtg42wtg42

openspec-new-change

Scaffold an OpenSpec change directory and fetch the first artifact template.

Community
Intermediate
jankneumannjankneumann
4

openspec-ff-change

Generate OpenSpec change artifacts and implementation scaffolds with dependency-aware sequencing.

Community
Advanced
fjpulidopfjpulidop
9

openspec-new-change

Scaffold OpenSpec change directories and guide first artifact creation.

Community
Advanced