openspec-new-change

Initialize a new OpenSpec change with an artifact-driven workflow.

Updated Jan 10, 2026

Search Tags:#automation #workflow #scaffolding #cli #openspec #change-management #artifact-workflow

Ready to run

npx skills add https://github.com/rick2047/WrestleGM --skill openspec-new-change-rick2047

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: openspec-new-change
Source: https://github.com/rick2047/WrestleGM/tree/main/.opencode/skills/openspec-new-change
Command: npx skills add https://github.com/rick2047/WrestleGM --skill openspec-new-change-rick2047

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

OpenSpec change management can be complex and error-prone; this skill provides a guided, artifact-driven workflow to initialize and organize a new change.

Core Features & Use Cases

Step-by-step scaffolding for a new OpenSpec change at openspec/changes/<name>.
Automatic guidance on selecting the workflow schema, creating the change directory, and querying artifact status.
Guardrails to prevent accidental artifact creation before user direction.

Quick Start

Describe the change you want to work on in kebab-case and I will guide you through creating a new OpenSpec change using the 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 create a new OpenSpec change directory using an artifact workflow?▼

OpenSpec change management begins by initializing a new change directory at openspec/changes/<name> using a kebab-case name. This guided workflow helps you select the appropriate schema and tracks artifact readiness throughout the process.

How does the OpenSpec artifact workflow handle schema selection?▼

The artifact workflow provides automatic guidance for selecting the correct workflow schema when initializing your OpenSpec change. It ensures the change directory is properly configured before you proceed with artifact creation.

Do I need to follow specific naming conventions for OpenSpec change management?▼

Yes, you must provide your change name in kebab-case format. The workflow uses this input to automatically scaffold the new change directory and organize the associated artifacts within the OpenSpec structure.

Does this OpenSpec workflow prevent accidental artifact creation?▼

Yes, the workflow includes built-in guardrails to prevent accidental or premature artifact creation. It ensures that artifacts are only generated after receiving explicit user direction during the guided initialization process.

What is the best way to track artifact readiness during an OpenSpec change?▼

The best way to track artifact readiness is to use this guided workflow, which automatically queries artifact statuses. It provides continuous visibility into whether required artifacts for your OpenSpec change are complete and ready.

When should I use an artifact-driven workflow for OpenSpec change management?▼

You should use an artifact-driven workflow when your team is adopting OpenSpec for feature development and change management. It reduces complexity and errors by providing a structured, step-by-step scaffolding process for initializing changes.