openspec-new-change

Scaffold a new OpenSpec change directory with artifact workflow instructions.

4|2|Updated Aug 27, 2025
One-click install
npx skills add https://github.com/finger-gun/sisu --skill openspec-new-change-finger-gun
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-new-change
Source: https://github.com/finger-gun/sisu/tree/main/.kilocode/skills/openspec-new-change
Command: npx skills add https://github.com/finger-gun/sisu --skill openspec-new-change-finger-gun

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Start a new OpenSpec change using the experimental artifact workflow. Use when the user wants to create a new feature, fix, or modification with a structured step-by-step approach.

Core Features & Use Cases

  • Scaffold a new OpenSpec change directory at openspec/changes/<name>/ using the selected workflow.
  • Auto-select a default workflow schema, create the change, show status, and fetch the first artifact instructions without performing changes yet.
  • Enforce guardrails: validate kebab-case change names, avoid creating duplicates, and clearly present next steps.
  • Example Use Case: A developer wants to start a new feature and follow a guided artifact-driven process to outline and draft the first artifact.

Quick Start

Run the openspec new change command to scaffold a new change and review 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 directory for a feature modification?

OpenSpec artifact workflow scaffolds changes at openspec/changes/<name>/ by selecting a default workflow schema, generating status checks, and fetching first artifact instructions to guide structured feature drafting.

What is the artifact workflow for managing development changes?

Artifact workflow is a structured, step-by-step approach for creating features or fixes that guides you through naming changes, selecting schemas, generating status checks, and obtaining sequential artifact instructions.

How do I start a structured change management process for a new fix?

Start structured change management by running openspec new change, which auto-selects a default workflow schema, scaffolds the change directory, evaluates status, and presents first artifact guidance without performing changes.

What naming conventions are required for creating an OpenSpec change?

OpenSpec changes require kebab-case naming, and the workflow enforces guardrails to validate name formats and prevent creating duplicates of existing change directories.

Does the OpenSpec artifact workflow perform changes when scaffolding a new directory?

No, the OpenSpec artifact workflow scaffolds the change directory, shows status, and fetches first artifact instructions to outline next steps without performing actual code changes.

What's the best way to avoid duplicate change entries in a development workflow?

Use a guided artifact workflow that enforces guardrails checking for existing directories and validating kebab-case names before scaffolding new change entries to avoid duplicates.