openspec-new-change

Scaffolding an OpenSpec change requires providing a kebab-case name, which automatically generates the openspec/changes/<name> directory and applies the appropriate workflow schema to generate initial artifact templates for your feature proposal.

The artifact-driven workflow in OpenSpec change management automates change naming, schema selection, and artifact scaffolding to provide a repeatable lifecycle process with traceable artifacts from initial proposal to ready-to-implement status.

Yes, the OpenSpec CLI is required to use this workflow, as it supports the core steps for creating a new change, checking its status, and retrieving first-artifact instructions during the scaffolding process.

Yes, the workflow applies to creating new features, fixes, or modifications within OpenSpec projects, automatically determining and applying the appropriate workflow schema across multiple supported schemas.

You check the status of an OpenSpec change using the built-in status step supported by the OpenSpec CLI, which tracks the change lifecycle from initial proposal through artifact creation to a ready-to-implement state.

The workflow is limited to OpenSpec projects requiring the OpenSpec CLI, meaning it cannot be used for change management outside the supported schemas and artifact-driven lifecycle structure it scaffolds.