openspec-new-change

To scaffold a new change directory, describe your intended change and the workflow will structure the process under openspec/changes/<name> without prematurely creating artifacts. It sets up the directory using a default or specified workflow, presenting the first artifact instructions.

An artifact-driven workflow is a structured, repeatable process for managing changes that previews artifact status and templates before generating files. It enforces guardrails like validating kebab-case change names and prompting for missing input to ensure consistent progress reporting.

Validating a kebab-case change name is handled automatically by the scaffolding guardrails when you describe your change. The workflow checks the naming format, prompts for missing input if needed, and derives the change name to ensure it meets the required structure before proceeding.

Yes, you can preview the first artifact template without generating files. The scaffolding process presents the current status and the first artifact instructions directly, allowing you to review the template and structure before any actual artifacts are created in the directory.

Yes, the scaffolding process enforces guardrails that prompt for missing input and clearly report current progress. If required information is absent, it will request the missing details and display the workflow status, ensuring you know exactly what step to complete next.

The best way to start a structured change without prematurely creating artifacts is to use a scaffolding tool that sets up the change directory and previews the workflow status. This approach provides the first artifact instructions and enforces name validation, ensuring a repeatable entry point.