openspec-new-change

Starting a guided OpenSpec change workflow involves describing your intended feature or fix. The system then prompts for a kebab-case change name and optional schema, applying guardrails to ensure a structured artifact sequence without unintended directory creation.

An artifact-driven workflow ensures consistent structure for proposals, tasks, and modifications. It guides you through a defined sequence of prompts and validations to scaffold changes, preventing unstructured file creation.

Yes, you can inspect progress and retrieve first-artifact instructions without creating artifacts. The workflow provides commands to check artifact status and guide you through the initial scaffolding steps safely.

No, a specific schema is not required to start. The workflow supports default workflows out of the box, but allows optional schema selection if your change execution requires a customized artifact sequence.

Yes, the workflow implements guardrails to prevent unintended creation. It provides status checks and first-artifact instructions first, ensuring directories and artifacts are only created when you intentionally proceed.