openspec-new-change

Scaffold OpenSpec changes and fetch first artifact templates via CLI.

6|Updated Feb 5, 2026
One-click install
npx skills add https://github.com/jacobcy/vibe-coding-control-center --skill openspec-new-change-jacobcy
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-new-change
Source: https://github.com/jacobcy/vibe-coding-control-center/tree/main/.github/skills/openspec-new-change
Command: npx skills add https://github.com/jacobcy/vibe-coding-control-center --skill openspec-new-change-jacobcy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides a structured, artifact-driven way to start a new OpenSpec change so users can create feature, fix, or modification scaffolds without guessing the required artifacts or workflow steps.

Core Features & Use Cases

  • Guided Change Creation: Derives a kebab-case change name from a user's description or validates a provided name and creates a scaffolded change directory.
  • Workflow Selection & Visibility: Uses the default schema unless the user requests another, shows workflow/schema choices, and displays artifact readiness status.
  • First-Artifact Instructions: Retrieves and presents the template and context for the first ready artifact so contributors can draft content without accidentally creating artifacts.
  • Use Case: A developer wants to open a spec-driven feature change; the skill scaffolds openspec/changes/<name>/, shows which artifacts are pending, and prepares the first artifact template for them to draft.

Quick Start

Use the openspec CLI to create a new change by giving a kebab-case name or describing the change and then ask to show the first artifact instructions.

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 or fix?

To scaffold an OpenSpec change, provide a kebab-case name or a description of the modification. The workflow creates a change directory at openspec/changes/<name>/ and prepares the first artifact template.

What is the artifact-driven workflow for creating an OpenSpec change?

The artifact-driven workflow structures change creation by scaffolding required artifacts sequentially. It derives a kebab-case name, creates the directory, and retrieves the first ready artifact template without automatically creating the artifacts.

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

Yes, you need the openspec CLI available in your system PATH. The skill relies on the CLI to create the scaffolded change directory and fetch the initial artifact templates and status.

Can I select a specific workflow schema when scaffolding an OpenSpec change?

Yes, the skill uses the default schema by default but allows you to request another. It displays available workflow and schema choices alongside the artifact readiness status during initialization.

How does OpenSpec handle the first artifact template during change creation?

OpenSpec retrieves and presents the template and context for the first ready artifact. This allows contributors to draft content manually without accidentally creating artifacts in the openspec/changes/<name>/ directory.