openspec-new-change

Create OpenSpec changes with kebab-case names and workflow schemas.

221|96|Updated May 18, 2022
One-click install
npx skills add https://github.com/SAP/e-mobility-charging-stations-simulator --skill openspec-new-change-sap
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-new-change
Source: https://github.com/SAP/e-mobility-charging-stations-simulator/tree/main/.opencode/skills/openspec-new-change
Command: npx skills add https://github.com/SAP/e-mobility-charging-stations-simulator --skill openspec-new-change-sap

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates starting a new OpenSpec change using the experimental artifact workflow, providing a structured path from naming to artifact guidance for new feature, fix, or modification work.

Core Features & Use Cases

  • Guided change creation: Establish a new OpenSpec change with a clear kebab-case name and the appropriate workflow schema.
  • Artifact-driven workflow: Orchestrates the steps to scaffold the change, monitor artifact readiness, and fetch first artifact instructions.
  • Iterative development support: Enables you to progressively complete artifacts while maintaining a repeatable setup process.

Quick Start

  • Ensure your change name follows kebab-case (e.g., add-feature-x).
  • Decide whether to use the default workflow schema or specify a different one.
  • Create the change scaffold, e.g.: openspec new change "<name>".
  • Check the artifact status, e.g., openspec status --change "<name>".
  • Retrieve instructions for the first ready artifact, e.g.: openspec instructions <first-artifact-id> --change "<name>".
  • When ready, provide direction to proceed with the next steps.

Frequently Asked Questions about openspec-new-change

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

FAQPage Schema
How do I start a new OpenSpec change using the artifact-driven workflow?

To start an OpenSpec change, run `openspec new change "<name>"` with a kebab-case name. This scaffolds the change directory using the default or explicit workflow schema and prepares the first artifact for guidance.

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

The OpenSpec artifact-driven workflow orchestrates change creation by scaffolding a named change, monitoring artifact readiness via status checks, and fetching instructions to progressively complete each required artifact.

Do I need a specific CLI tool to scaffold an OpenSpec change?

Yes, the OpenSpec CLI is required to scaffold changes, validate kebab-case naming, select workflow schemas, and retrieve artifact instructions. The CLI manages the entire artifact readiness and guidance lifecycle.

How do I check artifact status after creating an OpenSpec change?

Check artifact status by running `openspec status --change "<name>"`. This monitors which artifacts are ready for processing, allowing you to retrieve instructions for the first available artifact using `openspec instructions`.

What naming convention does OpenSpec validate when creating a new change?

OpenSpec requires kebab-case naming for new changes, such as `add-feature-x`. The CLI validates this format during scaffold creation to ensure consistency across the artifact-driven workflow.