openspec-new-change

Scaffold new OpenSpec changes with kebab-case naming and workflow schema.

Updated Apr 6, 2026
One-click install
npx skills add https://github.com/ybenitezf/pi-github --skill openspec-new-change-ybenitezf
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-new-change
Source: https://github.com/ybenitezf/pi-github/tree/main/.opencode/skills/openspec-new-change
Command: npx skills add https://github.com/ybenitezf/pi-github --skill openspec-new-change-ybenitezf

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the kickoff of a new OpenSpec change workflow, providing a clean, guided start instead of ad-hoc setup.

Core Features & Use Cases

  • Structured scaffolding: creates a scaffolded change at openspec/changes/<name>/ with a clear artifact sequence.
  • Status-driven guidance: shows artifact readiness and provides instructions for the first artifact without creating anything yet.
  • Guardrails: enforces kebab-case naming convention and uses the default workflow schema unless requested.

Quick Start

Describe what you want to build in kebab-case, then run openspec new change "<name>" to scaffold the change.

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 workflow from scratch?

To scaffold an OpenSpec change, run openspec new change "<name>" with a kebab-case name. This creates a structured scaffold at openspec/changes/<name>/ and provides status-driven guidance for the first artifact without making destructive changes.

What is the default workflow schema used when creating an OpenSpec change?

The default workflow schema is applied automatically when creating an OpenSpec change unless a specific schema is requested. This ensures a standardized artifact sequence and status-driven guidance for the new workflow.

Does OpenSpec change scaffolding require a specific naming convention?

Yes, OpenSpec change scaffolding enforces kebab-case naming conventions. You must provide a kebab-case name when running the openspec new change command to ensure proper directory and artifact creation.

Can I preview artifact status before committing to an OpenSpec change scaffold?

Yes, the OpenSpec change scaffold is non-destructive and shows artifact readiness before any files are created. It provides instructions for the first artifact and waits for user confirmation before taking action.

What's the best way to automate change management for new features in OpenSpec?

Use the openspec new change command to automate change management kickoff for new features or fixes. It guides naming, schema selection, and artifact status checks, providing a clean structured start instead of ad-hoc setup.