openspec-new-change

To start an OpenSpec change, provide a concise description or name. The scaffold automates directory creation, derives a kebab-case name, and guides you through the artifact lifecycle without creating artifacts initially.

Artifact-driven planning structures feature requests and fixes using a repeatable process. It scaffolds a change directory and provides the first artifact template to guide collaborative planning sessions across teams.

Yes, the OpenSpec workflow enforces kebab-case naming conventions for change directories. It applies guardrails and prompts to ensure safe status interactions and proper schema selection during planning.

Yes, you can use an optional workflow schema to guide the artifact process. The scaffold supports optional schema selection to structure modifications, fixes, or features according to your team's requirements.

The scaffold provides the first artifact template but does not create artifacts itself. This limitation ensures safe status interactions during initial planning, requiring you to manually generate artifacts in subsequent steps.

The best way to support multi-user planning is using an artifact-driven workflow. It provides clear next steps, enforces naming conventions, and offers templates to align teams during collaborative change proposals.