openspec-propose

To generate a change proposal in one step, run openspec new change with a description. It automatically scaffolds the openspec/changes directory and creates proposal.md, design.md, and tasks.md artifacts.

Automated scaffolding for change proposals eliminates manual file coordination by generating standardized proposal, design, and task documents. You need it when planning software changes that require consistent tracking from description to implementation.

To create a kebab-case change name, provide a natural language description of your desired change. The workflow derives a kebab-case name automatically, scaffolds the directory, and coordinates artifact generation without manual naming.

Yes, you can track implementation progress after generating artifacts by running openspec status. This checks the scaffolding created under openspec/changes and monitors the workflow status of your generated proposal, design, and tasks.

Openspec workflow requires no external dependencies to scaffold changes. It operates independently to derive kebab-case names, scaffold directories under openspec/changes, and coordinate artifact creation through built-in commands and status checks.

The best way to plan software changes without multiple tool invocations is using an automated end-to-end workflow. It scaffolds a complete change proposal with design and task artifacts in one step, ensuring fast and consistent planning.