openspec-new-change

Scaffold an OpenSpec change and present the first artifact template.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/brianzzs/GreenFiveInnings --skill openspec-new-change-brianzzs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-new-change
Source: https://github.com/brianzzs/GreenFiveInnings/tree/main/.opencode/skills/openspec-new-change
Command: npx skills add https://github.com/brianzzs/GreenFiveInnings --skill openspec-new-change-brianzzs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Many contributors struggle to start a well-formed OpenSpec change with the correct workflow, artifact sequence, and naming conventions; this Skill provides a guided, repeatable process to scaffold a change and surface the first artifact instructions without accidentally creating or committing artifacts.

Core Features & Use Cases

  • Guided Change Creation: Derives or validates a kebab-case change name from user input and instructs how to run the openspec CLI to scaffold the change.
  • Schema and Artifact Guidance: Chooses the default workflow schema unless the user requests another, queries schema options if asked, and shows the status and first-artifact template without creating artifacts.
  • Use Case: Ideal for spec authors or engineers who want to create a new feature, bugfix, or modification in an OpenSpec repository while preserving control and review of initial artifacts.

Quick Start

Ask: Start a new change named add-user-auth and show me the first artifact template using the default workflow.

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 an OpenSpec change and get the first artifact template?

To scaffold an OpenSpec change, provide a kebab-case name or description to derive one, then run the openspec CLI to initialize the workflow and display the first artifact template without creating it.

What is the artifact-driven workflow for OpenSpec change management?

The artifact-driven workflow is a structured, step-by-step process for OpenSpec change management that scaffolds changes and surfaces artifact instructions sequentially, ensuring contributors follow correct naming conventions and schema without accidentally committing artifacts.

Do I need the openspec CLI installed to start a new change scaffold?

Yes, using the openspec CLI requires it to be in your PATH to scaffold changes and query schema options. You must provide a kebab-case name or description to initialize the artifact workflow.

How do I use a custom workflow schema instead of the default for my OpenSpec change?

To use a custom workflow schema, explicitly request it when starting the OpenSpec change; otherwise, the default schema is applied automatically unless you ask to query available schema options.

Will starting a new OpenSpec change automatically create and commit my initial artifacts?

No, starting a new OpenSpec change inspects artifact readiness and only presents the first artifact template, ensuring no artifacts are automatically created or advanced beyond the initial scaffold.