openspec-new-change

Automates new OPSX change workflow initiation with templates and validation.

Updated Jan 29, 2026
One-click install
npx skills add https://github.com/hongquandev/OpenSpec-VI --skill openspec-new-change-hongquandev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-new-change
Source: https://github.com/hongquandev/OpenSpec-VI/tree/main/.agent/skills/openspec-new-change
Command: npx skills add https://github.com/hongquandev/OpenSpec-VI --skill openspec-new-change-hongquandev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides a guided, structured approach to starting a new change using the OPSX testing-artifact workflow. It helps teams initiate feature work, bug fixes, or adjustments with a repeatable process.

Core Features & Use Cases

  • Structured onboarding: Guides users through naming changes in kebab-case, selecting a default workflow schema, and creating a new change scaffold at openspec/changes/<name>/.
  • Artifact guidance: Provides status checks and instructions for generating the first artifact based on the chosen schema.
  • Guardrails & clarity: Ensures input validation, clear prompts, and safe execution steps without creating artifacts.

Quick Start

Tell me the change you want to start (in kebab-case) and I will guide you through creating the OPSX change skeleton and the first artifact template.

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 change workflow with structured artifact guidance?

To start a new change workflow, you provide a kebab-case name, and the system guides you through selecting a default schema and creating a change scaffold at openspec/changes/<name>/ with first-artifact instructions.

What is the OPSX workflow for initiating feature work or bug fixes?

The OPSX workflow provides a structured, step-by-step approach for initiating changes by enforcing input validation, creating change folders, and guiding artifact generation based on a chosen schema.

Do I need to format my change names in a specific way for the openspec workflow?

Yes, change names must be formatted in kebab-case to pass input validation and correctly generate the new change scaffold within the openspec directory structure.

Does the change management workflow automatically generate the first artifact?

No, the workflow provides status checks and instructions for generating the first artifact but executes safely without actually creating the artifacts itself.

What is the best way to ensure structured onboarding for a new software adjustment?

The best way is using a structured onboarding process that applies default workflow schemas, validates inputs, and creates repeatable change scaffolds for safe execution.