openspec-new-change

Scaffold OpenSpec changes with kebab-case names and workflow selection.

1|Updated May 22, 2022
One-click install
npx skills add https://github.com/jeffbalagosa/pick-or-shuffle --skill openspec-new-change-jeffbalagosa
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-new-change
Source: https://github.com/jeffbalagosa/pick-or-shuffle/tree/main/.gemini/skills/openspec-new-change
Command: npx skills add https://github.com/jeffbalagosa/pick-or-shuffle --skill openspec-new-change-jeffbalagosa

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It streamlines starting a new OpenSpec change by guiding users through naming, workflow selection, scaffold creation, and first artifact preparation, reducing setup friction and errors.

Core Features & Use Cases

  • Guided change creation: prompts for a kebab-case name and preferred workflow, then scaffolds the change directory.
  • Structured artifact planning: reveals the first artifact and keeps you informed on status without creating artifacts.
  • Guardrails and prompts: ensures valid input, handles existing changes, and provides clear next steps.

Quick Start

Create a new OpenSpec change scaffold with a kebab-case name using the openspec new change command.

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 for a feature or fix?

To scaffold an OpenSpec change, run the guided workflow to provide a kebab-case name and select a preferred workflow. The CLI then automatically creates the change directory and prepares the first artifact template for your engineering team.

How does guided workflow selection work when creating an OpenSpec change?

Guided workflow selection prompts you for a kebab-case name and preferred workflow type, then scaffolds the change directory accordingly. It ensures valid input and prevents duplicates before generating a frontmatter-based metadata entry and descriptive guide.

What is the best way to prevent duplicate artifacts when starting an OpenSpec workflow?

The best way to prevent duplicate OpenSpec artifacts is using an automated scaffold workflow that guards against invalid inputs and existing changes. It validates the kebab-case name before creating any directory structure or frontmatter metadata entry.

Does the OpenSpec change scaffold generate the first artifact automatically?

No, the OpenSpec change scaffold does not generate the first artifact automatically. It reveals the first artifact template and keeps you informed on status, providing clear next steps for structured artifact planning without creating the actual artifact.

Can I use kebab-case naming for any type of engineering improvement in OpenSpec?

Yes, you can use kebab-case naming for features, fixes, or improvements in OpenSpec. The guided workflow applies to engineering teams creating structured artifact sequences and validates the kebab-case input before scaffolding the change directory.