skills.rest
circlebacknever
circlebackneverCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

openspec-new-change

Creates a new OpenSpec change scaffold for requested features or fixes.

Updated Nov 29, 2022
Search Tags:#workflow#schema#scaffold#change management#openspec#artifact
One-click install
npx skills add https://github.com/circlebacknever/soundstage --skill openspec-new-change-circlebacknever
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-new-change
Source: https://github.com/circlebacknever/soundstage/tree/main/.codex/skills/openspec-new-change
Command: npx skills add https://github.com/circlebacknever/soundstage --skill openspec-new-change-circlebacknever

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes the guesswork from starting a new OpenSpec change by turning a vague request into a structured, step-by-step change scaffold.

Core Features & Use Cases

  • Change Setup: Creates a new change directory from a user-provided name or idea.
  • Workflow Selection: Uses the default workflow unless the user asks for a specific schema or wants to inspect available workflows.
  • Artifact Guidance: Shows the current change status and the first ready artifact so the user can begin with the right template.
  • Use Case: A developer wants to plan a feature, bug fix, or product tweak and needs the exact OpenSpec starting point before writing any artifacts.

Quick Start

Ask this skill to start a new OpenSpec change from your idea and it will create the change scaffold, show the status, and present the first artifact template.

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

To start an OpenSpec change, provide a valid kebab-case change name and the Skill will generate the structured change scaffold, display the setup status, and present the first artifact template for implementation.

What is an OpenSpec change scaffold and when do I need one?▼

An OpenSpec change scaffold is a structured directory setup for planning features, fixes, or modifications. You need it when you want to turn a vague request into a step-by-step workflow before writing any implementation artifacts.

Do I need the OpenSpec CLI to create a change directory?▼

Yes, you need access to the OpenSpec CLI to complete the guided setup. The Skill uses the CLI to create the change directory, select the appropriate schema, and inspect the initial workflow status.

Can I select a specific workflow schema for OpenSpec change management?▼

You can select a specific workflow schema for change management by requesting it during setup. If no specific schema is requested, the Skill defaults to the standard workflow to create your change scaffold.

How do I inspect the status of a newly created OpenSpec change?▼

To inspect the status of a newly created OpenSpec change, the Skill automatically shows the current status and the first ready artifact after generating the scaffold, allowing you to begin with the correct template.

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
kivo360kivo360
1

Orchestrating SPEC-First TDD Development

Orchestrate SPEC-first TDD workflows with SPEC, TEST, CODE, and DOC phases.

Community
Advanced
Max-LooMax-Loo
2

openspec-continue-change

Create the next OpenSpec change artifact after checking status and dependencies.

Community
Advanced
sgiathsgiath
4

openspec-new-change

Scaffold a new OpenSpec change directory with an artifact-driven workflow.

Community
Intermediate