openspec-new-change

To initiate an OpenSpec change, you start a structured, artifact-driven workflow that guides you step-by-step through defining new features or modifications. This process uses the OpenSpec CLI to manage change artifacts and generate initial instructions.

An artifact-driven workflow manages software changes by generating and tracking structured artifacts throughout the development process. Instead of unstructured commits, it uses the OpenSpec CLI to manage schemas and artifacts, ensuring a systematic approach to introducing new features or fixes.

Yes, you need the OpenSpec CLI installed to manage change artifacts and schemas. The CLI handles the underlying artifact-driven workflow, allowing you to initiate new features, fixes, or modifications within the OpenSpec framework.

You should use OpenSpec when you need a structured, step-by-step approach to define changes and modifications in your project. It is ideal for scenarios where you want to manage new features or fixes using an experimental, artifact-based system rather than ad-hoc methods.

The best way to start is by triggering the workflow to create a new change artifact specifically for the authentication feature. This initiates the structured process, allowing you to define the modification and receive the initial artifact instructions via the OpenSpec CLI.

Yes, you can use OpenSpec change management for modifications of any scale, but it applies a structured, artifact-driven workflow to every change. If your project requires systematic tracking for even small fixes, this framework provides the necessary schemas and step-by-step guidance.