openspec-new-change

To start a new OpenSpec change, initiate the artifact workflow with a kebab-case change name or descriptive request. The process creates the initial change directory, defines the workflow, and provides instructions for the first artifact.

An artifact-driven workflow structures development changes using predefined artifacts. OpenSpec leverages this approach to guide new features, fixes, or modifications through a step-by-step process, ensuring a structured initiation for every system change.

Yes, the OpenSpec change initiation accepts a descriptive request to derive a valid change name. You do not need to manually format the name; the framework processes the descriptive text to establish the new change directory.

Yes, OpenSpec optionally accepts a specific workflow schema when initiating a new change. This allows you to customize the structured, artifact-driven process beyond the default workflow configuration for your new feature or modification.

The best way to introduce a new feature is using the OpenSpec new change command. This scaffolds the initial change directory, applies an artifact-driven workflow, and outputs instructions for the first required artifact.

A structured change management process ensures artifact-driven development. OpenSpec streamlines this by scaffolding a dedicated change directory and guiding the workflow, which maintains consistency across new features, fixes, and modifications.