openspec-new-change

To scaffold an OpenSpec change directory without generating artifacts, describe the desired change. The workflow validates change names, suggests default schemas, and previews artifact status before safely pausing to prevent file generation.

The OpenSpec change scaffolding process is used to safely begin a new modification workflow. It handles workspace setup, change naming, default workflow selection, and provides first-artifact instruction templates while safely preventing artifact generation.

Yes, you can preview artifact status before creating a new OpenSpec change. The scaffolding workflow checks artifact statuses and validates change names, ensuring your workspace setup is correct before any artifacts are actually generated.

To start a new OpenSpec workflow using CLI or scripts, initiate a new change request. The scaffolding process covers naming conventions, schema handling, and workspace setup, stopping safely before artifacts are generated to provide clear next steps.

You should not use an artifact-free workflow for OpenSpec changes when you need to immediately generate and commit files to your repository. This scaffolding approach intentionally stops before creation to validate naming and preview schemas safely.