opsx-new

Create OpenSpec change directories from kebab-case change names.

Updated May 25, 2026
One-click install
npx skills add https://github.com/ywh0606/chat-robot --skill opsx-new-ywh0606
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: opsx-new
Source: https://github.com/ywh0606/chat-robot/tree/main/.claude/skills/opsx-new
Command: npx skills add https://github.com/ywh0606/chat-robot --skill opsx-new-ywh0606

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes the manual setup work required when starting a new OpenSpec change by creating the correct change directory structure automatically.

Core Features & Use Cases

  • Change Scaffold Creation: Creates a new OpenSpec change directory from a provided kebab-case change name.
  • Workflow Guidance: Shows the created change status and provides the next steps for adding proposal, design, and task artifacts.
  • Use Case: When beginning a feature request or project modification, use this Skill to initialize the OpenSpec change workspace before creating detailed artifacts.

Quick Start

Use the opsx-new skill to create a new OpenSpec change directory named add-user-auth.

Frequently Asked Questions about opsx-new

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create an OpenSpec change directory for a new feature request?

To create an OpenSpec change directory, you provide a kebab-case change name to initialize the structured change scaffold automatically before planning and implementation.

What is an OpenSpec change scaffold used for in software development?

An OpenSpec change scaffold is used to initialize a structured directory workspace for project modifications, serving as the foundation before creating detailed proposal, design, and task artifacts.

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

Yes, you need the openspec CLI installed, as the Skill requires it to create the change directories and display the resulting change status information.

What format should the change name be in when creating an OpenSpec scaffold?

The change name must be provided in kebab-case format to successfully generate the OpenSpec change directory structure.

What are the next steps after generating an OpenSpec change directory?

After generating the change directory, the next steps involve adding proposal, design, and task artifacts to the newly created workspace as guided by the displayed change status.