openspec-new-change

To start an OpenSpec change, you provide a kebab-case name and the Skill scaffolds a change directory while surfacing the first artifact plan instructions without creating artifacts.

The artifact-driven process is an experimental workflow that scaffolds a dedicated change directory and outlines an initial artifact plan to guide feature, fix, or modification work systematically.

Yes, the OpenSpec CLI is required to scaffold a new change directory, as the workflow follows defined CLI steps to validate the kebab-case name and prepare the initial artifact plan.

Validating a kebab-case name for an OpenSpec change is handled automatically by the workflow, which checks the provided name format before deciding on a schema and scaffolding the directory.

No, the OpenSpec scaffold does not create artifacts automatically; it prepares the directory and surfaces the first artifact instructions, then uses a stop-and-wait prompt for your direction.

You should use the artifact-driven workflow for software fixes when you need a guided, repeatable process to ensure a clean scaffold, reducing miscommunication and rework during planning.