openspec-new-change

Scaffold a new OpenSpec change workflow with schema selection and status checks.

4|1|Updated Jan 16, 2026
One-click install
npx skills add https://github.com/jankneumann/agentic-coding-tools --skill openspec-new-change-jankneumann
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-new-change
Source: https://github.com/jankneumann/agentic-coding-tools/tree/main/.agents/skills/openspec-new-change
Command: npx skills add https://github.com/jankneumann/agentic-coding-tools --skill openspec-new-change-jankneumann

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Starting an OpenSpec change often requires manual setup and consistent scaffolding. This Skill provides a standardized workflow to initialize a new change, ensuring schema choices, status checks, and artifact instructions are prepared without premature artifact creation.

Core Features & Use Cases

  • Standardized change scaffolding: creates a new change directory with the appropriate schema (unless the user requests a non-default workflow).
  • Status and instruction provisioning: shows the current artifact status and fetches instructions for the first artifact.
  • Guardrails and validation: validates kebab-case name, prevents overwriting existing changes, and prevents automatic artifact creation.

Quick Start

Run openspec new change "<name>" to scaffold a new OpenSpec change and then follow the prompts to specify the 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 OpenSpec change for feature planning?

Run openspec new change followed by your change name to initialize a new OpenSpec change scaffold, which sets up the directory structure and guides you through schema selection without creating artifacts automatically.

What is the OpenSpec change workflow for initiating fix proposals?

The OpenSpec change workflow is a standardized scaffolding process that initializes changes, validates status, and fetches first artifact instructions to ensure consistent setup for feature or fix proposals.

Does the OpenSpec new change command validate change names?

Yes, the OpenSpec new change command validates that your change name uses kebab-case format and prevents overwriting existing change directories to maintain artifact workflow integrity.

Can I automatically generate artifacts during OpenSpec change initialization?

No, you cannot automatically generate artifacts during initialization; the workflow fetches instructions for the first artifact and presents the current status, but leaves artifact creation to you.

What limitations exist when using the OpenSpec new change scaffolding tool?

Limitations of the OpenSpec new change scaffolding include the prevention of automatic artifact creation and strict enforcement of kebab-case naming, meaning you must manually follow prompts to proceed with the artifact workflow.