openspec-new-change

Scaffold a new OpenSpec change and return the first artifact template.

Updated Apr 22, 2026
One-click install
npx skills add https://github.com/dentedgem9846-claw/chronocrystal-opsx --skill openspec-new-change-dentedgem9846-claw
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-new-change
Source: https://github.com/dentedgem9846-claw/chronocrystal-opsx/tree/main/.pi/skills/openspec-new-change
Command: npx skills add https://github.com/dentedgem9846-claw/chronocrystal-opsx --skill openspec-new-change-dentedgem9846-claw

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides a structured, non-destructive way to kick off OpenSpec changes using the experimental artifact workflow. It guides users through a deterministic change-scaffold process, captures intent in a kebab-case name, and surfaces the first artifact template without applying any changes.

Core Features & Use Cases

  • Initiates a new OpenSpec change scaffold using the experimental artifact workflow.
  • Derives a kebab-case change name from user-provided descriptions.
  • Presents a clear, step-by-step plan and the first artifact template without creating any artifacts.

Quick Start

Describe the change you want to build using a kebab-case name to begin scaffolding the new OpenSpec change.

Frequently Asked Questions about openspec-new-change

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

FAQPage Schema
How do I scaffold a new OpenSpec change using a structured workflow?

Scaffolding an OpenSpec change involves submitting a kebab-case name or description to initiate the workflow. The system then returns a status update and the first artifact template, guiding you step-by-step without creating any artifacts.

What is the OpenSpec artifact workflow for change management?

The OpenSpec artifact workflow is a structured, non-destructive process for initiating features or fixes. It captures intent in a kebab-case name and surfaces artifact templates sequentially to plan modifications deterministically.

Do I need a kebab-case name to start an OpenSpec change scaffold?

Yes, a kebab-case change name or description is required to begin. The workflow derives the kebab-case identifier from your input to initiate the structured change-scaffold process.

Does the OpenSpec change scaffold create artifacts automatically?

No, the OpenSpec change scaffold does not create artifacts automatically. It is a non-destructive workflow that only presents a step-by-step plan and returns the first artifact template for review.

Can I use OpenSpec workflow automation for fixing existing modifications?

Yes, OpenSpec workflow automation scaffolds changes for fixes, features, or modifications. It provides a guided, step-by-step approach to structure your change intent.

What is the best way to manage a new feature change with OpenSpec?

The best way to manage a new feature change with OpenSpec is using the experimental artifact workflow. It offers a deterministic change-scaffold process that captures intent and presents templates without applying changes.