openspec-new-change

To scaffold a new OpenSpec change, describe the desired feature implementation and the tool will generate a standardized change skeleton at openspec/changes/<name>. This scaffold includes a default workflow, status reporting, and first-artifact instructions without creating any artifacts until you confirm.

An artifact-driven workflow in OpenSpec change management provides a standardized, traceable process for feature development. It creates a ready-to-use change skeleton that guides teams through the artifact lifecycle, ensuring changes remain reproducible and governed throughout implementation.

Yes, you can use OpenSpec to manage fixes and enhancements without generating artifacts immediately. The tool surfaces first-artifact readiness instructions and waits for your explicit confirmation before creating any artifacts within the change scaffold.

OpenSpec change scaffolding is designed for both developers and product teams adopting the OpenSpec CLI. It streamlines starting new changes by applying a consistent, artifact-driven scaffold that governs feature development across the entire team.

The best way to start tracking feature changes using the OpenSpec CLI is to initiate a new change scaffold. This applies a default artifact-driven workflow at openspec/changes/<name>, making changes traceable and reproducible while providing status reporting.

You should not use an automated scaffold for OpenSpec changes if your project does not adopt the OpenSpec CLI or lacks an openspec/changes directory structure. The tool relies on this specific artifact workflow to enforce traceability and standardized governance.