openspec-new-change

Name: openspec-new-change
Availability: InStock
Author: TheLegendTubaGuy

Automates starting an OpenSpec change with artifact-driven workflow templates.

33|5|Updated Feb 24, 2026

Search Tags:#workflow #planning #cli #scaffold #openspec #artifact #change

Ready to run

npx skills add https://github.com/thelegendtubaguy/Qidi-Max-4-Optimized --skill openspec-new-change-thelegendtubaguy

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: openspec-new-change
Source: https://github.com/thelegendtubaguy/Qidi-Max-4-Optimized/tree/main/.pi/skills/openspec-new-change
Command: npx skills add https://github.com/thelegendtubaguy/Qidi-Max-4-Optimized --skill openspec-new-change-thelegendtubaguy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Start a new OpenSpec change using the experimental artifact workflow to provide a structured, repeatable way to propose features, fixes, or modifications.

Core Features & Use Cases

Artifact-driven planning: scaffolds a change directory, derives a kebab-case name, and guides you through the artifact lifecycle.
Guardrails and prompts: enforces naming conventions, optional schema selection, and safe status interactions without creating artifacts.
Collaborative planning: supports multi-user planning with clear next steps and artifact templates.

Quick Start

Provide a concise change description or name and I will begin the OpenSpec change scaffold.

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 request with a structured workflow?▼

To start an OpenSpec change, provide a concise description or name. The scaffold automates directory creation, derives a kebab-case name, and guides you through the artifact lifecycle without creating artifacts initially.

What is artifact-driven planning for software feature requests?▼

Artifact-driven planning structures feature requests and fixes using a repeatable process. It scaffolds a change directory and provides the first artifact template to guide collaborative planning sessions across teams.

Does the OpenSpec workflow enforce naming conventions for change artifacts?▼

Yes, the OpenSpec workflow enforces kebab-case naming conventions for change directories. It applies guardrails and prompts to ensure safe status interactions and proper schema selection during planning.

Can I use a schema to guide the artifact workflow for software modifications?▼

Yes, you can use an optional workflow schema to guide the artifact process. The scaffold supports optional schema selection to structure modifications, fixes, or features according to your team's requirements.

What are the limitations of scaffolding a change directory without creating artifacts?▼

The scaffold provides the first artifact template but does not create artifacts itself. This limitation ensures safe status interactions during initial planning, requiring you to manually generate artifacts in subsequent steps.

What's the best way to support multi-user planning sessions for software changes?▼

The best way to support multi-user planning is using an artifact-driven workflow. It provides clear next steps, enforces naming conventions, and offers templates to align teams during collaborative change proposals.