openspec-new-change

Scaffolding a new OpenSpec change requires running the command to create the directory structure at openspec/changes/<name> with initial metadata. It provides status updates, first-artifact instructions, and guardrails without creating the actual artifacts.

The artifact-driven workflow is a structured, step-by-step process for creating features, fixes, or amendments. It automates scaffolding the change directory and supplies guidance for generating the initial artifact according to the chosen workflow.

Yes, creating a new OpenSpec change scaffold requires the OpenSpec CLI. The CLI automates the generation of the openspec/changes/<name> directory structure and enforces the input validation guardrails.

OpenSpec validates change names by enforcing kebab-case formatting during the scaffolding process. This input validation ensures safe steps and consistent naming conventions before generating the directory structure.

No, the OpenSpec scaffolding process does not create the first artifact automatically. It produces the scaffold and provides instructions and guardrails for the user to follow the artifact-driven workflow manually.

Use an automated scaffold when starting a new feature, bug fix, or modification to ensure a repeatable process. It eliminates manual errors by providing a consistent template and guided steps for the artifact-driven workflow.