openspec-new-change

Creates a new OpenSpec change scaffold for a feature, fix, or modification request.

Updated Jan 26, 2026
One-click install
npx skills add https://github.com/brandon-setegn/kafka-test --skill openspec-new-change-brandon-setegn
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-new-change
Source: https://github.com/brandon-setegn/kafka-test/tree/main/.cursor/skills/openspec-new-change
Command: npx skills add https://github.com/brandon-setegn/kafka-test --skill openspec-new-change-brandon-setegn

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you start a new OpenSpec change without guessing the workflow, ensuring you create the right scaffold and know exactly what comes next.

Core Features & Use Cases

  • Change Scaffolding: Creates a new change directory with the selected workflow schema.
  • Workflow Discovery: Helps you inspect available schemas when you need to choose the right process.
  • First Artifact Guidance: Shows the status and instructions for the first ready artifact so you can begin correctly.
  • Use Case: A product team wants to propose a feature, fix, or modification in a structured way and needs the initial OpenSpec setup before drafting content.

Quick Start

Ask the assistant to start a new OpenSpec change for your feature or fix, and provide a clear name or short description of what you want to build.

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 structured change management workflow for a new feature?

To start structured change management, create a new OpenSpec change scaffold by selecting a workflow schema, setting up the change directory, and following the first-artifact guidance provided. This ensures you initiate the specification process correctly without guessing the workflow steps.

What is OpenSpec change scaffolding and when do I need it?

OpenSpec change scaffolding is a structured planning process that creates a dedicated directory and schema for proposing features, fixes, or modifications. You need it when you want to establish a standardized specification workflow before drafting any actual project content.

Do I need the openspec CLI to create a new change directory?

Yes, creating a new OpenSpec change directory requires the openspec CLI. The Skill relies on this command-line tool to inspect available schemas, scaffold the change directory, and execute supporting change status and instruction commands.

How do I choose the right workflow schema for my modification request?

You can choose the right workflow schema by using the Skill's workflow discovery feature to inspect available schemas. This helps you evaluate the structured planning options and select the process that best fits your specific feature, fix, or modification request.

What's the best way to propose a fix using a structured specification workflow?

The best way to propose a fix is to ask the assistant to start a new OpenSpec change with a clear name or short description. This automatically scaffolds the change directory and shows the status and instructions for the first ready artifact so you can begin documenting correctly.