openspec-new-change

To start an OpenSpec change, describe the feature or fix to trigger the guided artifact workflow, which validates a kebab-case name and generates a scaffolded change directory at openspec/changes/<name>/ without creating artifacts immediately.

The artifact workflow is a schema-driven sequence that structures OpenSpec changes step-by-step. It determines the artifact progression, shows readiness status, and provides tailored instructions for the first artifact to ensure traceability and consistency.

To fix invalid name errors during OpenSpec change creation, ensure your change name uses kebab-case formatting. The workflow enforces this naming convention as a guardrail to validate inputs and prevent directory conflicts before generating the scaffold.

No, the OpenSpec change workflow does not create artifacts immediately. It generates an actionable change scaffold with status guidance and instructions for the first artifact, allowing you to progress through the schema-driven sequence step-by-step.

If an existing OpenSpec change is detected with the same name, the workflow's guardrails identify the conflict and ask for direction. This prevents overwriting active changes and ensures traceability across your structured artifact progression.

Yes, you can specify a custom schema for the OpenSpec artifact workflow when requesting a change. If no schema is specified, the workflow defaults to its standard artifact sequence to determine the step-by-step progression within the change directory.