skills.rest
runtime-env
runtime-envOFFICIAL
Explore all skills by this author →
GitHub

openspec-new-change

Scaffold OpenSpec change directories with kebab-case naming and workflow schemas.

47|2|Updated Oct 30, 2023
Search Tags:#automation#workflow#CLI#scaffold#openspec#change-management#artifact-workflow
One-click install
npx skills add https://github.com/runtime-env/runtime-env --skill openspec-new-change-runtime-env
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-new-change
Source: https://github.com/runtime-env/runtime-env/tree/main/.gemini/skills/openspec-new-change
Command: npx skills add https://github.com/runtime-env/runtime-env --skill openspec-new-change-runtime-env

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill streamlines initiating OpenSpec changes by providing a guided, artifact-driven workflow that standardizes setup and context.

Core Features & Use Cases

  • Scaffold a new change directory openspec/changes/<name> with kebab-case naming.
  • Determine and apply the default or requested workflow schema.
  • Show artifact status and provide instructions for the first artifact.
  • Stop and wait for user direction, without creating artifacts yet.

Quick Start

Open a new change scaffold with openspec new change "<name>". Check progress with openspec status --change "<name>". Retrieve the first artifact instructions with openspec instructions <first-artifact-id> --change "<name>".

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 change directory in OpenSpec?▼

Scaffold a new OpenSpec change directory by running the CLI command `openspec new change "<name>"`, which creates the change folder under `openspec/changes/` using kebab-case naming.

What is the OpenSpec change workflow for starting new features?▼

The OpenSpec change workflow is an artifact-driven process that standardizes setup by validating names, selecting schemas, generating scaffolds, and providing first-artifact instructions to guide feature modifications safely.

How do I check the status of an OpenSpec change?▼

Check OpenSpec change status using the command `openspec status --change "<name>"`, which displays the current artifact progression and scaffold state for the specified change.

Can I use spaces or uppercase letters when naming an OpenSpec change?▼

No, OpenSpec change naming enforces strict kebab-case formatting, meaning names must be lowercase and use hyphens instead of spaces or underscores to pass validation.

Does the OpenSpec scaffold automatically generate artifacts for my change?▼

No, the scaffold generation stops and waits for user direction without creating artifacts, ensuring safe stepwise progression before preparing any artifact templates.

How do I fetch instructions for the first artifact in an OpenSpec change?▼

Retrieve first artifact instructions by running `openspec instructions <first-artifact-id> --change "<name>"`, which provides the guidance needed to proceed with the workflow.

Related Skills

Explore More Software Engineering Skills→
inflexa-aiinflexa-ai
29

openspec-new-change

Scaffold new change directories and manage artifact dependencies with openspec CLI.

Official
Intermediate
rockdongrockdong

openspec-new-change

Scaffold an OpenSpec change directory with a selected workflow schema.

Community
Intermediate
aehrcaehrc
133

openspec-apply-change

Implement OpenSpec change tasks and update progress automatically.

Official
Advanced
elasticelastic
208

openspec-new-change

Scaffold a new OpenSpec change with a kebab-case name and workflow schema.

Official
Advanced