openspec-new-change

To start a new development change, you need a structured scaffolding workflow that creates a dedicated directory and applies a schema. This approach initiates the change and provides the template for your first artifact automatically.

Yes, you need a feature branch to scaffold a new OpenSpec change. A feature branch is required for operation, alongside the OpenSpec CLI, to ensure your changes are isolated before the workflow scaffolding begins.

An artifact-driven workflow structures development changes by requiring specific artifacts to be created and documented sequentially. It solves the problem of starting new tasks by scaffolding a clear directory structure and guiding the initial proposal artifact.

Yes, you can start a new change using just a description. The workflow supports deriving an explicit change name from your provided description, applying a default workflow schema if a specific one is not designated.

The best way to manage scaffolding for these changes is using an artifact-driven approach that supports explicit naming and purposes. It automatically applies a selected or default workflow schema to structure the change directory from the outset.