openspec-new-change

To start an OpenSpec change, run `openspec new change "<name>"` to scaffold the directory, then check artifact status with `openspec status --change "<name>"` and fetch instructions with `openspec instructions <first-artifact-id> --change "<name>"`.

An artifact-driven workflow structures feature development by guiding you through sequential artifacts. This skill scaffolds the change directory and retrieves the first artifact instructions to ensure structured setup instead of ad-hoc modifications.

No, the OpenSpec change workflow does not create artifacts automatically during setup. It provides CLI instructions to orchestrate the process and retrieve the first artifact guidelines, enabling planning and stakeholder alignment before generation.

Yes, you can select a specific workflow schema when scaffolding an OpenSpec change. The skill enforces the default workflow schema unless you explicitly request a custom schema during the change initiation process.

Your OpenSpec change name needs to be kebab-case to ensure consistent directory naming and artifact routing. The skill guides you through deriving a kebab-case name to maintain structured workflow paths.

The best way to manage change planning is using the OpenSpec CLI to scaffold changes and check artifact status. This approach provides instructions without generating artifacts, allowing stakeholders to align before development proceeds.