openspec-new-change

Scaffolding a new OpenSpec change creates a directory at openspec/changes/<name> using an artifact-driven workflow. It applies a default schema automatically, but you can override it with a specific workflow if requested.

An artifact-driven workflow for change management provides a reproducible, guided process to scaffold changes. It surfaces artifact statuses and generates the first-artifact template without creating artifacts until explicit user direction is given.

You preview the first artifact template by describing your desired change. The tool surfaces artifact statuses and the exact first-artifact template without creating any artifacts, preventing premature file generation until you provide explicit direction.

Yes, you can override the default workflow schema when scaffolding OpenSpec changes. The tool determines the default behavior but allows you to explicitly request and apply a specific schema to suit your change management needs.

Your OpenSpec change artifact is not created automatically because the tool enforces guardrails for safe, auditable changes. It prompts for user direction and prevents artifact creation until you explicitly provide that direction.

Yes, OpenSpec change scaffolding is suitable for product teams needing reproducible setups. It replaces ad-hoc change management with a repeatable, artifact-driven process that guides developers through safe and auditable change creation.