openspec-new-change

To scaffold an OpenSpec change, describe the feature or fix you want to build. The workflow guides you through deriving a kebab-case name, selecting a schema, and providing first artifact instructions without creating files until you confirm.

The artifact-driven workflow is a structured process for initiating OpenSpec changes. It guides users through naming, schema selection, and status checks, outputting the first artifact template and a prompt to proceed before any actual artifacts are created.

Yes, you can specify a custom schema when creating an OpenSpec change. The workflow selects a default schema automatically but allows you to request a different one to fit your specific change-management requirements.

You provide a natural language description of your feature or modification, and the workflow automatically derives a kebab-case change name from your input to ensure standardized naming for your OpenSpec artifacts.

No, the OpenSpec change workflow includes safe guardrails to ensure no artifacts are created until user confirmation. It only provides the first artifact template, current status, and location details for you to review first.

The best way to kick off a structured feature modification is to use the guided OpenSpec change workflow. It scaffolds the change step by step, showing the chosen schema, current status, and first artifact instructions for safe initiation.