openspec-new-change

Scaffold an OpenSpec change directory and validate kebab-case names.

5|1|Updated Apr 8, 2026
One-click install
npx skills add https://github.com/Catsofsuffering/CCGS --skill openspec-new-change-catsofsuffering
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-new-change
Source: https://github.com/Catsofsuffering/CCGS/tree/main/.agents/skills/openspec-new-change
Command: npx skills add https://github.com/Catsofsuffering/CCGS --skill openspec-new-change-catsofsuffering

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps users reliably initialize a new OpenSpec change by scaffolding the change directory, selecting or confirming the workflow schema, and presenting the first artifact's instructions without creating artifacts prematurely.

Core Features & Use Cases

  • Guided change initialization: Ask clarifying questions to derive a valid kebab-case change name or accept a user-provided name, and validate against existing changes.
  • Workflow and schema handling: Use the default schema unless a specific schema is requested and offer schema listing when asked to "show workflows".
  • Artifact inspection: Run status and fetch the first ready artifact's instructions so the user can review and approve content before any artifact creation.
  • Use Case: Product managers or spec authors can quickly scaffold a new feature spec, confirm the workflow, and preview the initial artifact template before delegating work to Agent Teams.

Quick Start

Start a new OpenSpec change named add-user-auth using the experimental artifact workflow and show the instructions 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 spec?

To scaffold an OpenSpec change, you provide a feature name which the tool validates as kebab-case, checks for existing change conflicts, and generates the change directory along with status output.

What is the OpenSpec artifact-driven workflow?

The OpenSpec artifact-driven workflow is an experimental process that initializes a change directory, confirms a workflow schema, and presents the first ready artifact template for review before any actual artifact creation begins.

How do I initialize a new OpenSpec change using the CLI?

You initialize a new change by running the openspec CLI with a specified feature name, allowing the tool to scaffold the directory, apply the default schema, and fetch the initial artifact instructions.

Do I need the openspec CLI to create a change directory?

Yes, the openspec CLI is required to create the change directory, validate kebab-case naming conventions against existing changes, and inspect the first artifact template without premature creation.

Can I preview the first artifact template before creating it in OpenSpec?

Yes, the tool fetches the first ready artifact's instructions so you can review and approve the content, ensuring you inspect the template before any artifact is actually created.

How do I show available workflows and schemas in OpenSpec?

You can show available workflows by requesting a schema listing, otherwise the tool applies the default schema during the change initialization process unless a specific schema is requested.