opsx-new-change

Create OpenSpec change directories and retrieve artifact instructions via the openspec CLI.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps users avoid manually organizing new software changes by providing a structured OpenSpec workflow for creating and preparing change artifacts.

Core Features & Use Cases

  • Change Initialization: Creates a new OpenSpec change directory from a user-provided feature, fix, or modification request.
  • Workflow Guidance: Determines the correct schema, checks artifact status, and retrieves the instructions for the first required artifact.
  • Use Case: A developer planning a new authentication feature can use this Skill to scaffold the change process and receive the correct next-step artifact guidance.

Quick Start

Ask the skill to start a new change for the feature or fix you want to build.

Frequently Asked Questions about opsx-new-change

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

FAQPage Schema
How do I start a structured change workflow for new software features?

To start a structured change workflow, you provide a feature or fix request to initialize a new change directory. The workflow then determines the correct schema, checks artifact status, and retrieves instructions for the first required artifact.

What is artifact-driven planning in software development?

Artifact-driven planning is a development process that requires creating structured artifacts to guide software changes. It helps developers avoid manually organizing modifications by scaffolding the change process and providing step-by-step guidance for required artifacts.

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

You create an OpenSpec change directory by asking the skill to start a new change based on your feature, fix, or modification request. It uses the openspec CLI workflow to initialize the directory and retrieve instructions for the first artifact.

Do I need the openspec CLI to initialize change workflows?

Yes, you need the openspec CLI to initialize change workflows. The skill requires the openspec CLI workflow to create change directories, inspect artifact status, and retrieve artifact instructions during the change initialization process.

Can I use this workflow to scaffold both bug fixes and new features?

Yes, you can use this workflow to scaffold both bug fixes and new features. It accepts user-provided feature, fix, or modification requests to create a structured OpenSpec change directory and apply the correct schema for artifact planning.

What is the best way to prepare artifact instructions for software modifications?

The best way to prepare artifact instructions is to use a structured OpenSpec change workflow. It checks the current artifact status and retrieves the specific instructions needed for the next required artifact, ensuring modifications are properly planned.