openspec-new-change

Bootstrap a new OpenSpec change with kebab-case naming and schema selection.

3|1|Updated Feb 1, 2026
One-click install
npx skills add https://github.com/moltbook-experiments/glasshouse-protocol --skill openspec-new-change-moltbook-experiments
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-new-change
Source: https://github.com/moltbook-experiments/glasshouse-protocol/tree/main/.github/skills/openspec-new-change
Command: npx skills add https://github.com/moltbook-experiments/glasshouse-protocol --skill openspec-new-change-moltbook-experiments

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a standardized, guided process to start a new OpenSpec change using an experimental artifact workflow, reducing setup time and ensuring consistent architecture across changes.

Core Features & Use Cases

  • Provides a step-by-step scaffold for creating a new OpenSpec change, including schema selection and naming validation.
  • Automatically reports artifact readiness and provides first-artifact instructions to kick off development.
  • Use Case: A team wants to bootstrap a feature or fix with a repeatable, auditable process.

Quick Start

Follow the prompts to create a new change with the OpenSpec CLI, review the generated scaffold, and then proceed to generate the first artifact template.

Frequently Asked Questions about openspec-new-change

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I bootstrap a new OpenSpec change with a structured workflow?

To bootstrap a new OpenSpec change, you use a guided, artifact-driven workflow that initializes the repository, reports status, and generates the first artifact template while enforcing kebab-case naming and schema selection.

What is an artifact-driven development workflow for feature scaffolding?

An artifact-driven development workflow provides a standardized, step-by-step scaffold for creating changes, ensuring consistent architecture and generating auditable artifact templates to kick off development.

How do I enforce kebab-case naming when creating a development artifact?

You enforce kebab-case naming by requiring a valid change name in kebab-case format before the OpenSpec CLI scaffolds the repository and prepares the first artifact template.

Do I need any specific CLI tools to scaffold an OpenSpec change?

Yes, you need the openspec CLI to scaffold the repository, report artifact readiness status, and prepare the first artifact templates for the new change.

What's the best way to standardize feature setup across a development team?

The best way to standardize feature setup is using a guided scaffold that validates naming, selects schemas, and automatically reports artifact readiness, ensuring a repeatable and auditable process.

Can I use OpenSpec to generate templates for project initialization?

Yes, OpenSpec can generate first-artifact templates during project initialization, providing step-by-step instructions to kick off development after you review the generated scaffold.