What is OpenSpec New Change?

OpenSpec New Change is a skill that helps developers initiate new features or modifications using a structured, step-by-step workflow within the OpenSpec framework.

How do I start using this skill?

Simply describe the change you want to implement, and the skill will guide you through the process of creating a new change directory and managing artifacts.

Can I specify a custom workflow schema?

Yes, if you have a specific schema in mind, you can mention it, and the skill will use that schema for the change process.

What happens if I provide an invalid change name?

If the change name is not in kebab-case format, the skill will prompt you to provide a valid name before proceeding.

Is this skill suitable for quick changes?

This skill is best for structured development processes rather than quick, ad-hoc changes, as it emphasizes a guided workflow.

OpenSpec New Change

Name: OpenSpec New Change
Availability: InStock
Author: fission-ai

Free

Streamline your feature development with guided workflows.

by fission-ai64.5k stars on fission-ai/openspec

1 views

Updated Aug 7, 2026

Get this skill

Free · Opens the source repo

What OpenSpec New Change does

OpenSpec New Change is designed for developers who want to create new features or modifications in a structured manner using the OpenSpec framework. This skill leverages an artifact-driven approach, allowing users to initiate a new change by providing a clear name or description of what they want to build. The process is guided step-by-step, ensuring that users do not miss any critical aspects of their development workflow.

The skill begins by prompting the user to describe the change they wish to implement. Based on this input, it generates a kebab-case name for the change, which is essential for maintaining consistency and clarity in the project. Users can also specify a store if they are working within a registered OpenSpec repository, which helps in organizing and managing changes across different projects.

Once the change name is established, the skill creates a dedicated change directory and provides the current status of the artifact workflow. It identifies the first artifact that needs to be addressed and retrieves instructions for its creation. This ensures that users have a clear understanding of what is required to move forward, without proceeding to create artifacts prematurely. The skill emphasizes clarity and user direction, making it an ideal tool for developers looking to maintain a structured approach to feature development.

OpenSpec New Change is particularly beneficial for teams that follow a disciplined development process and need a reliable method to manage changes systematically. By utilizing this skill, developers can enhance their productivity and ensure that all necessary steps are followed in their workflow, reducing the risk of oversight or errors during development.

When to use it

Use this skill when you want to start a new feature, bug fix, or modification in a systematic way using OpenSpec.

When not to use it

This skill is not suitable for ad-hoc changes or when a quick, unstructured approach is needed for development.

What you can build with it

Starting a New Feature

When you need to implement a new feature, use this skill to ensure all steps are followed systematically.

Managing Bug Fixes

Utilize the structured approach to manage bug fixes effectively, preventing oversight during development.

Collaborating in Teams

Ideal for teams that require a consistent workflow for changes, ensuring everyone follows the same process.

How to install OpenSpec New Change

View source

1. Install with the skills CLI

npx skills add fission-ai/openspec/openspec-new-change --agent claude-code

2. Or install it manually

Download the skill folder and drop it into ~/.claude/skills/ for all projects, or .claude/skills/ to scope it to one repo. Restart Claude Code so it picks up the new skill.

Anthropic's agentic coding CLI, and the reference implementation of Agent Skills. Drop a skill folder into ~/.claude/skills and Claude Code loads it automatically whenever a task matches the skill's description. Claude Code docs

Inside SKILL.md

Written by fission-ai

Start a new change using the experimental artifact-driven approach.

Store selection: If the user names a store (a store is a standalone OpenSpec repo registered on this machine) or the work lives in one, run openspec store list --json to discover registered store ids, then pass --store <id> on the commands that read or write specs and changes (new change, status, instructions, list, show, validate, archive, doctor, context, view). Once selected, treat --store <id> as sticky for the rest of the workflow. Every unscoped example of those commands below is shorthand: before running it, append the flag. For example, run openspec status --change "<name>" --json --store "<id>", not the unscoped form shown below. Other commands do not take the flag. Hints printed by commands already carry the flag; keep it on follow-ups. Without a store, commands act on the nearest local openspec/ root.

Input: The user's request should include a change name (kebab-case) OR a description of what they want to build.

Steps

If no clear input provided, ask what they want to build

Ask the user (open-ended, no preset options):

"What change do you want to work on? Describe what you want to build or fix."

From their description, derive a kebab-case name (e.g., "add user authentication" → add-user-auth).

IMPORTANT: Do NOT proceed without understanding what the user wants to build.
Determine the workflow schema

Use the default schema (omit --schema) unless the user explicitly requests a different workflow.

Use a different schema only if the user mentions:
- A specific schema name → use --schema <name>
- "show workflows" or "what workflows" → run openspec schemas --json and let them choose
Otherwise: Omit --schema to use the default.
Create the change directory
```
openspec new change "<name>"
```
Add --schema <name> only if the user requested a specific workflow. This creates a scaffolded change in the planning home resolved by the CLI.
Show the artifact status
```
openspec status --change "<name>" --json
```
Use the returned planningHome, changeRoot, artifactPaths, and nextSteps instead of assuming repo-local paths.
Get instructions for the first artifact The first artifact depends on the schema (e.g., proposal for spec-driven). Check the status output to find the first artifact with status "ready".
```
openspec instructions <first-artifact-id> --change "<name>"
```
This outputs the template and context for creating the first artifact.
STOP and wait for user direction

Output

After completing the steps, summarize:

Change name and location
Schema/workflow being used and its artifact sequence
Current status (0/N artifacts complete)
The template for the first artifact
Prompt: "Ready to create the first artifact? Just describe what this change is about and I'll draft it, or ask me to continue."

Guardrails

Do NOT create any artifacts yet - just show the instructions
Do NOT advance beyond showing the first artifact template
If the name is invalid (not kebab-case), ask for a valid name
If a change with that name already exists, suggest continuing that change instead
Pass --schema if using a non-default workflow

Frequently asked questions about OpenSpec New Change

Similar skills

Rhino 3D Scripting

Streamline your Rhinoceros 3D scripting tasks.

MVVM Toolkit

Streamline ViewModel development with source generators.

FreeCAD Scripts

Generate Python scripts for FreeCAD automation and modeling.

Azure Architecture Builder

Design and deploy Azure infrastructure using natural language.

Command Development

Streamline your command creation for Claude Code.

Create Cowork Plugin

Easily build and package plugins through guided sessions.