openspec-new-change

To start a new OpenSpec change, this skill automates scaffolding a change directory and provides guided instructions for generating artifacts using the default workflow. It reduces manual setup time and errors when initializing structured feature changes.

Scaffolding OpenSpec change artifacts is best handled by automating the creation of a new change directory with a default artifact workflow ready for the first artifact. This ensures consistent naming and process structure for teams deploying new features.

Yes, the OpenSpec CLI is required to automate this change management workflow. The skill relies on the CLI to adhere to the default artifact workflow, scaffold the change directory, and provide step-by-step guidance for generating and managing artifacts.

Yes, teams deploying new features can use this to quickly initialize a structured change with consistent naming and a guided process. It creates a default artifact-driven workflow ready for the first artifact to reduce setup time.

An artifact-driven workflow for OpenSpec change management provides step-by-step guidance to generate and manage change artifacts consistently. This structured approach reduces setup errors and ensures consistent process adherence across team feature deployments.

No, openspec-new-change adheres to the default artifact workflow to scaffold the change and provide guided instructions. It automates starting a structured OpenSpec change using this default artifact-driven approach without custom workflow configurations.