openspec-propose

To generate a structured change proposal, describe your build or fix idea and provide a kebab-case change name. The system scaffolds a new change directory and creates a proposal.md artifact capturing the what and why of your project planning.

An OpenSpec proposal artifact is a structured markdown document that outlines what software change you want to build and why. You need one when starting a specs workflow to create a design-ready outline before moving into implementation tasks.

You create an implementation-ready workflow handoff by running the propose flow with your described build or fix. It deterministically generates the proposal.md artifact and reports status, telling you exactly what commands to run next for design and specs.

Yes, you need the openspec CLI installed to ensure compatibility when creating change proposals. The deterministic artifact generation strictly validates your input and relies on the CLI environment to scaffold the change directory correctly.

Automated proposal generation is limited to producing the proposal.md artifact only. It does not create the design, specs, or tasks artifacts directly, requiring you to run subsequent workflow commands manually to continue the planning process.

Yes, you can and should use kebab-case names for change management directories. The input validation requires strict kebab-case formatting for the change name to successfully scaffold the directory and generate the proposal artifact.