skills.rest
g1331
g1331COMMUNITY
Explore all skills by this author →
GitHub

openspec-new-change

Guide users through creating an OpenSpec change with the artifact workflow.

3|Updated Nov 25, 2025
Search Tags:#cli#scaffold#openspec#workflow-automation#software-engineering#change-management#artifact-workflow
One-click install
npx skills add https://github.com/g1331/AutoRouter --skill openspec-new-change-g1331
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-new-change
Source: https://github.com/g1331/AutoRouter/tree/main/.claude/skills/openspec-new-change
Command: npx skills add https://github.com/g1331/AutoRouter --skill openspec-new-change-g1331

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill guides users through starting a new OpenSpec change using the experimental artifact workflow, providing a structured, step-by-step approach to define change scope, select schemas, scaffold, and track progress.

Core Features & Use Cases

  • Guided change creation: prompts for a kebab-case change name, selects an appropriate workflow schema, and scaffolds the change directory.
  • Artifact status awareness: explains how to inspect progress and identify the first ready artifact without committing changes.
  • Safe, non-destructive orchestration: presents guardrails and stops before creating artifacts, ensuring user direction at each step.

Quick Start

Provide a kebab-case change name to start the guided 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 a structured workflow?▼

The guided workflow provides a safe, non-destructive scaffold for OpenSpec changes by stopping before creating artifacts, ensuring you direct the process and maintain status visibility at each step.

What is the OpenSpec artifact workflow for change management?▼

It solves the problem of unstructured software modifications by applying guardrails and stopping before creating artifacts, ensuring user direction and safe orchestration throughout the change lifecycle.

How do I track progress and identify ready artifacts in an OpenSpec workflow?▼

This ensures safe, non-destructive orchestration by presenting guardrails at each step, stopping before artifact creation to confirm user direction.

Do I need to format my OpenSpec change name in a specific way?▼

This naming convention is required to initiate the structured step-by-step process for defining feature, fix, or modification scopes.

Does the OpenSpec change workflow automatically commit artifacts during scaffolding?▼

You can inspect progress and identify the first ready artifact while maintaining complete control over the modification process.

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
manishsinghmfmanishsinghmf

openspec-new-change

Initialize a new OpenSpec change with artifact-driven scaffolding and status tracking.

Community
Advanced
hellyaxshellyaxs

openspec-archive-change

Archive completed OpenSpec changes after validating artifacts and tasks.

Community
Advanced
Yager-42Yager-42

openspec-new-change

Automate starting an OpenSpec change with a kebab-case name and scaffold.

Community
Advanced