openspec-new-change

Initialize a new OpenSpec change with an artifact workflow scaffold.

45|3|Updated Jan 20, 2026
One-click install
npx skills add https://github.com/Charles5277/nuxt-supabase-starter --skill openspec-new-change-charles5277
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-new-change
Source: https://github.com/Charles5277/nuxt-supabase-starter/tree/main/.claude/skills/openspec-new-change
Command: npx skills add https://github.com/Charles5277/nuxt-supabase-starter --skill openspec-new-change-charles5277

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

OpenSpec change creation can be error-prone without a standardized workflow. This skill provides a guided, artifact-driven scaffold to start a new feature, fix, or modification using the experimental artifact workflow.

Core Features & Use Cases

  • Provides a repeatable, scaffolded process for initiating OpenSpec changes.
  • Validates input naming and schema choices, and outlines the initial artifact sequence.
  • Useful for teams adopting OpenSpec to reduce onboarding time and ensure consistency.

Quick Start

Run the openspec new change <name> to scaffold a new OpenSpec 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 initiate a new OpenSpec change for a feature request or fix?

To initiate a new OpenSpec change, run the openspec new change command with a kebab-case name. This scaffolds a standardized artifact workflow, guiding schema selection and generating a ready-to-use first artifact template.

What is the artifact workflow for OpenSpec change management?

The OpenSpec artifact workflow is a scaffolded, repeatable process for creating changes like features or fixes. It enforces naming conventions, validates schema choices, and outlines an initial artifact sequence to reduce onboarding errors and ensure consistency.

How do I name a new OpenSpec change correctly?

You must name a new OpenSpec change using kebab-case formatting. The guided workflow validates this input along with your schema choice to ensure the change artifact sequence initializes without naming errors.

Do I need any dependencies to scaffold an OpenSpec change?

No external dependencies are required to scaffold an OpenSpec change. The workflow operates independently to validate naming, apply default guardrails, and generate the initial artifact template for your development process.

What is the best way to standardize OpenSpec change creation across a team?

The best way to standardize OpenSpec change creation is using a guided artifact workflow. It enforces guardrails like default workflow usage and consistent naming, reducing onboarding time and preventing error-prone manual scaffolding.

Can I use the OpenSpec workflow for both modifications and bug fixes?

Yes, the OpenSpec workflow applies to feature requests, fixes, or modifications. It provides the same guided artifact sequence and schema validation regardless of the change type being initialized.