openspec-new-change

Scaffold OpenSpec changes with kebab-case names and first artifact templates.

1|Updated Feb 22, 2026
One-click install
npx skills add https://github.com/SiddharthChillale/cloud-operations-reasoning-agent --skill openspec-new-change-siddharthchillale
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-new-change
Source: https://github.com/SiddharthChillale/cloud-operations-reasoning-agent/tree/main/.opencode/skills/openspec-new-change
Command: npx skills add https://github.com/SiddharthChillale/cloud-operations-reasoning-agent --skill openspec-new-change-siddharthchillale

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes uncertainty when initiating a new OpenSpec change by guiding users through naming, workflow selection, and obtaining the first artifact template without creating artifacts prematurely. It helps ensure the change is scaffolded correctly, validates kebab-case names, and prevents accidental artifact creation.

Core Features & Use Cases

  • Interactive Input Validation: Prompts the user if the change name is missing or not valid kebab-case and derives a suitable name from a natural-language description.
  • Workflow Schema Handling: Uses the default schema unless the user requests a specific one, with instructions to list and choose schemas when asked.
  • Scaffold and Preview: Runs the openspec CLI to create a scaffolded change directory and shows the status and the template for the first artifact without creating any artifacts.
  • Guardrails: Enforces name validation, avoids making or committing artifacts, and stops after providing the first artifact template to wait for explicit user confirmation.
  • Use Case: A spec author wants to start a new feature; the Skill scaffolds openspec/changes/<name>, shows which artifacts are required, and provides the template for the next step.

Quick Start

Create a new change by giving a kebab-case name or describing the feature you want and I will scaffold the change and show the template for the first artifact.

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 without creating artifacts prematurely?

To scaffold an OpenSpec change, provide a kebab-case name or natural-language description. The workflow creates the change directory, shows required artifacts, and previews the first artifact template without generating content.

What is an artifact-driven change workflow in OpenSpec?

An artifact-driven change workflow uses a schema to define required artifacts for a feature or fix. It scaffolds a change directory, validates kebab-case naming, and provides templates sequentially rather than generating content automatically.

How do I select or preview a workflow schema when starting an OpenSpec change?

OpenSpec applies the default workflow schema automatically unless you request a specific one. You can list available schemas and choose one before scaffolding the change directory and previewing the first artifact template.

Does the OpenSpec CLI require kebab-case naming for new change scaffolds?

Yes, the OpenSpec CLI enforces kebab-case naming for new change scaffolds. If a name is missing or invalid, it prompts for input or derives a valid kebab-case name from a natural-language feature description.

Why does my OpenSpec change stop after showing the first artifact template?

OpenSpec stops after showing the first artifact template as a guardrail to prevent accidental artifact creation. It waits for explicit user confirmation before proceeding to generate or commit any artifact content.

Can I use OpenSpec to scaffold a fix or modification instead of a new feature?

Yes, OpenSpec scaffolds changes for features, fixes, or modifications equally. You provide a kebab-case name or description, and it creates the change directory and previews the first artifact template regardless of change type.