openspec-new-change

Generate a new OpenSpec change scaffold with a derived kebab-case name and validate its uniqueness.

Updated Feb 4, 2026
One-click install
npx skills add https://github.com/SQDR2/PortableConversationScriptAssistant --skill openspec-new-change-sqdr2
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-new-change
Source: https://github.com/SQDR2/PortableConversationScriptAssistant/tree/main/.github/skills/openspec-new-change
Command: npx skills add https://github.com/SQDR2/PortableConversationScriptAssistant --skill openspec-new-change-sqdr2

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill streamlines creating a new OpenSpec change by providing a guided, artifact-driven workflow to scaffold and organize work before implementation.

Core Features & Use Cases

  • Automates the initial setup for new OpenSpec changes, deriving a kebab-case name from user input.
  • Chooses the appropriate workflow schema, scaffolds the change at openspec/changes/<name>, and tracks which artifacts remain to be created.
  • Supports a guided, repeatable process that reduces setup time and standardizes project structure for open specification changes.

Quick Start

Describe the change you want to work on and I will generate a kebab-case name, prepare the change directory, and outline the first artifact steps.

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 automatically?

To scaffold a new OpenSpec change, the tool derives a kebab-case name from your request, validates it does not already exist, and initializes the change directory under openspec/changes/<name> with the appropriate workflow schema.

What is the best way to generate a kebab-case name for an OpenSpec project setup?

The best way to generate a kebab-case name for an OpenSpec project setup is to describe the change you want. The tool automatically derives the kebab-case identifier from your natural language input and validates its uniqueness before scaffolding.

How does the OpenSpec artifact workflow handle the initial change setup?

The OpenSpec artifact workflow handles initial change setup by creating the scaffold directory, tracking remaining artifacts, and providing the first artifact's template without creating any artifacts until you direct it to proceed.

Do I need to manually create artifacts when bootstrapping an OpenSpec change?

No, you do not need to manually create artifacts when bootstrapping an OpenSpec change. The tool reports which artifacts need to be created and provides the first template, waiting for your direction before generating any actual artifact files.

Can I choose a specific workflow schema when creating a new OpenSpec change?

Yes, you can choose a specific workflow schema when creating a new OpenSpec change. The tool selects the default or explicitly requested workflow schema to initialize the change scaffold under the openspec/changes directory.

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

Your OpenSpec change scaffold stops after showing the first artifact template because the tool is designed to provide the template without creating artifacts yet, asking for your direction to proceed with the remaining artifact generation steps.