openspec-new-change

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

Updated Apr 11, 2026
One-click install
npx skills add https://github.com/rafazafar/codex-octopus --skill openspec-new-change-rafazafar
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-new-change
Source: https://github.com/rafazafar/codex-octopus/tree/main/.agents/skills/openspec-new-change
Command: npx skills add https://github.com/rafazafar/codex-octopus --skill openspec-new-change-rafazafar

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Facilitates initiating a new OpenSpec change by guiding users through a structured artifact-driven workflow, capturing input, creating a change scaffold, and sequencing artifacts.

Core Features & Use Cases

  • Derive a kebab-case change name from user input and scaffold a new OpenSpec change directory.
  • Validate change names, guard against duplicates, and present first-artifact instructions without creating artifacts.
  • Orchestrate an artifact-driven workflow using the experimental artifact workflow as a repeatable template.

Quick Start

Run the OpenSpec CLI to create a new change scaffold for the user's request.

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 directory from user input?▼

To scaffold an OpenSpec change directory, the system derives a kebab-case change name from your input, validates the format, and sets up the change scaffold with status and first-artifact instructions.

What is an artifact-driven workflow for change management?▼

An artifact-driven workflow for change management sequences structured project artifacts, guiding teams through capturing input, creating a change scaffold, and orchestrating subsequent artifact creation steps.

Does the OpenSpec change scaffolding process validate change names and detect duplicates?▼

Yes, OpenSpec change scaffolding validates the change name format to ensure it is kebab-case, detects existing changes to guard against duplicates, and reports guidance without creating artifacts.

How do I start a new change management workflow using kebab-case naming conventions?▼

You start a change management workflow by running the OpenSpec CLI, which captures your request, derives a kebab-case change name, and scaffolds the initial change directory and status.

What happens if I try to create an OpenSpec change with an invalid name format?▼

If the name format is invalid, the OpenSpec change workflow validates the input, rejects non-kebab-case strings, and reports guidance to correct the format without creating any artifacts.

Can I use the OpenSpec CLI to create artifacts automatically when starting a new change?▼

No, the OpenSpec CLI scaffolds the change directory and presents first-artifact instructions, but it does not create artifacts automatically, ensuring you follow the structured artifact workflow manually.