openspec-new-change

Scaffold new OpenSpec changes with npx openspec and input validation.

Updated Feb 3, 2026
One-click install
npx skills add https://github.com/ishibata91/ai-translation-engine-2 --skill openspec-new-change-ishibata91
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-new-change
Source: https://github.com/ishibata91/ai-translation-engine-2/tree/main/.agent/skills/openspec-new-change
Command: npx skills add https://github.com/ishibata91/ai-translation-engine-2 --skill openspec-new-change-ishibata91

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

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

Core Features & Use Cases

  • Guided change scaffolding for new features, fixes, or modifications within an OpenSpec project.
  • Artifact-driven workflow that outlines the sequence of artifacts, validations, and user prompts.
  • Input validation and prompts to ensure kebab-case change names and workspace readiness.

Quick Start

Run npx openspec new change "<name>" from the workspace root and follow the prompts to define the change.

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

To start an OpenSpec change, run npx openspec new change "<name>" from the workspace root and follow the interactive prompts to scaffold the modification. This automates creating a structured, step-by-step artifact workflow for your project change.

What is the artifact workflow in OpenSpec change management?

The OpenSpec artifact workflow is a structured, step-by-step approach for defining new features, fixes, or modifications. It guides you through a sequence of artifacts and validations to ensure your project change is properly scaffolded and documented.

Do I need to name my OpenSpec change in kebab-case?

Yes, OpenSpec requires kebab-case naming for new changes. The skill validates your input names before proceeding to ensure they meet the required formatting standard for the artifact workflow scaffolding process.

Can I use OpenSpec to scaffold changes outside the project root directory?

No, you must run the OpenSpec change scaffolding command from the workspace root. The tool requires the workspace to be in the OpenSpec root directory to properly validate and generate the artifact workflow for your new change.

What's the best way to structure a new modification in an OpenSpec workspace?

The best way to structure a new modification is using the experimental artifact workflow via npx openspec. This provides guided change scaffolding, outlining the sequence of artifacts, validations, and user prompts needed for your feature or fix.

Why does my OpenSpec change scaffolding fail during input validation?

OpenSpec change scaffolding fails during input validation if your change name is not in kebab-case or if you are not running the command from the OpenSpec workspace root directory. Ensure your workspace is properly configured before proceeding.