skills.rest
kamansoft
kamansoftOFFICIAL
Explore all skills by this author →
Website𝕏@kamansoftGitHub

openspec-new-change

Create a new OpenSpec change with a name or description.

Updated Mar 23, 2026
Search Tags:#command line#change management#OpenSpec#workflow initiation#schema-driven development
One-click install
npx skills add https://github.com/kamansoft/vite-plugin-flatwave-react --skill openspec-new-change-kamansoft
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-new-change
Source: https://github.com/kamansoft/vite-plugin-flatwave-react/tree/main/.cursor/skills/openspec-new-change
Command: npx skills add https://github.com/kamansoft/vite-plugin-flatwave-react --skill openspec-new-change-kamansoft

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires openspec, and includes scripts (resource) components.

What problem does it solve?

The OpenSpec change workflow is complex and often overwhelming for new users. This skill helps by initiating a new change with minimal input, providing clear next steps, and avoiding confusion about how to proceed.

Core Features & Use Cases

  • Streamlined Initiation: Create a new OpenSpec change with just a change name or a brief description.
  • Guided Workflow: Provides step-by-step instructions based on the chosen workflow schema.
  • Automated Setup: Sets up the necessary directories and metadata for the new change.

Quick Start

Initiate a new change for a feature using the openspec-new-change skill: "Create a new feature 'add-user-authentication' using the experimental artifact workflow."

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 from the command line?▼

You can start an OpenSpec change workflow by providing a change name or brief description to the skill, which then determines the appropriate schema and creates the required directory structure automatically.

What is schema-driven development in OpenSpec change management?▼

Schema-driven development in OpenSpec involves selecting a specific workflow schema to guide the creation of structured changes, ensuring directories and metadata are set up correctly from the start.

Do I need the openspec CLI installed to initiate a new change?▼

Yes, you must have the openspec CLI installed and accessible in your environment, as the skill depends on it to automate the setup of directories and metadata for your new change.

Can I create a new OpenSpec change with just a brief feature description?▼

Yes, you can initiate a new change using only a brief feature description, and the workflow will automatically determine the appropriate schema and provide step-by-step instructions.

What's the best way to avoid confusion when initiating complex OpenSpec changes?▼

Using a streamlined initiation process that accepts minimal input and provides clear, step-by-step instructions based on the chosen workflow schema is the best way to avoid overwhelming setup confusion.

Related Skills

Explore More Software Engineering Skills→
cli-agent-speccli-agent-spec
5

cli-agent-readiness

Score CLI agent-readiness across documentation, self-description, integration, setup, and workflows.

Official
Advanced
joannanowakowskajoannanowakowska

openspec-propose

Generate OpenSpec change proposals with design and task artifacts.

Community
Advanced
jasonkneenjasonkneen
471

apple-reminders

Manage Apple Reminders via remindctl terminal commands.

Community
Basic
docs-plusdocs-plus
88

scaffold-exercises

Generate standardized exercise directory structures with required subfolders and stub files.

Official
Intermediate