openspec-new-change

To start a new change in an artifact-driven workflow, you provide a change name or description to scaffold the necessary directory structure and generate initial artifact templates.

An artifact-driven workflow for change management structures development around generating specification files and templates, ensuring new features are defined by concrete artifacts created in a scaffolded directory before implementation begins.

Yes, the openspec CLI must be installed and configured to scaffold new change directories, as it provides the underlying framework required to determine the workflow schema and generate the artifact structure.

Yes, custom workflow schemas like TDD are supported when scaffolding a new change. The skill determines the appropriate workflow schema from your input and provides specific instructions for creating the first artifact.

The best way to define a new feature specification using OpenSpec is to scaffold the change directory and follow the provided artifact templates, ensuring your feature definition follows a structured, artifact-driven path.

Using an artifact-driven approach for starting new development changes ensures a structured path for defining specifications, streamlining the initiation process by providing clear templates and directory scaffolding for new features.