openspec-new-change

To start an OpenSpec change workflow, you provide a description of the feature or fix to derive a kebab-case change name, select a schema, and the CLI scaffolds the initial setup with status instructions.

The OpenSpec change management process uses an artifact-driven workflow to scaffold new modifications step-by-step, deriving a kebab-case name and selecting the appropriate schema without automatically creating artifacts.

Yes, you need the OpenSpec CLI installed to scaffold a new change, as the workflow relies on it to determine the schema and set up the initial structure for your modifications.

Yes, you can specify an optional schema preference when initializing an OpenSpec change workflow to ensure the scaffolding aligns with your specific feature or fix requirements.

No, the OpenSpec scaffolding workflow does not automatically generate artifacts; it enforces guardrails by providing status reports and next step instructions to handle changes gracefully.

Change names are formatted into kebab-case when starting an OpenSpec workflow, derived directly from your input descriptions to ensure consistent artifact-driven file naming.