openspec-new-change

Coordinates creation of a new OpenSpec change via artifact-driven workflow.

30|6|Updated Jan 26, 2026
One-click install
npx skills add https://github.com/tatargabor/wt-tools --skill openspec-new-change-tatargabor
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-new-change
Source: https://github.com/tatargabor/wt-tools/tree/main/.claude/skills/openspec-new-change
Command: npx skills add https://github.com/tatargabor/wt-tools --skill openspec-new-change-tatargabor

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Start a structured workflow to initialize a new OpenSpec change, guiding users through input collection, scaffolding, and artifact preparation without creating artifacts yet.

Core Features & Use Cases

  • Guided initiation of a new OpenSpec change with an artifact-driven workflow.
  • Automatic scaffolding of the change directory and status reporting for artifacts.
  • Interactive prompts and safeguards to ensure correct kebab-case naming and schema selection.

Quick Start

Initialize a new OpenSpec change using the default workflow and view the first artifact instructions without generating artifacts.

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 workflow for a feature or fix?

To start an OpenSpec change workflow, use this Skill to guide input collection, select the correct schema, and scaffold the change directory. It prevents artifact creation until explicitly directed.

What is the OpenSpec artifact-driven workflow process?

The OpenSpec artifact-driven workflow coordinates change initiation by collecting inputs, selecting schemas, scaffolding directories, and templating the first artifact. It requires the default workflow unless a specific schema is requested.

Does OpenSpec change scaffolding create artifacts automatically?

No, OpenSpec change scaffolding does not create artifacts automatically. It scaffolds the directory and reports status, preventing artifact creation until the user provides explicit direction.

How do I ensure correct kebab-case naming when initializing an OpenSpec change?

To ensure correct kebab-case naming during OpenSpec change initialization, the workflow uses interactive prompts and safeguards. This validates the naming convention before proceeding with schema selection and scaffolding.

Can I use a custom schema instead of the default workflow for OpenSpec changes?

Yes, you can request a specific schema for your OpenSpec change. The workflow applies the default schema automatically unless a custom schema is explicitly requested during the input collection phase.

What are the limitations of the OpenSpec change initiation workflow?

The main limitation is that the workflow stops before artifact creation, requiring explicit user direction to proceed. It also enforces strict kebab-case naming and default schema selection unless overridden.