openspec-new-change

To bootstrap a new OpenSpec change, you provide a kebab-case change name and optional workflow schema. The guided process enforces default schema usage and safe pauses before artifact creation to ensure repeatable, auditable changes.

OpenSpec change management requires kebab-case naming for all new artifacts. This guardrail enforces consistent directory structure and artifact sequencing, reducing setup drift and miscommunication across development teams.

You can provide an optional workflow schema when scaffolding OpenSpec changes. If omitted, the system applies a default schema to align artifact sequencing and directory structure with best practices.

OpenSpec pauses before artifact creation to request explicit user confirmation. This safety guardrail ensures transparent status checks and prevents unintended directory structure changes during the artifact-driven workflow.

OpenSpec change bootstrap operates without external dependencies. The deterministic, artifact-driven workflow provides tailored first-artifact instructions and status updates independently within your developer environment.

An artifact-driven workflow for OpenSpec change management scaffolds initial directory structures and enforces artifact sequencing. It standardizes kickoff processes, reducing setup drift by aligning naming, schema, and status checks.