openspec-propose

To generate a change proposal with design specs and tasks in one step, provide a kebab-case name or a descriptive sentence. The skill outputs ready-to-implement artifacts like proposal.md, design.md, and tasks.md automatically.

An automated change proposal workflow includes generating proposal.md, design.md, and tasks.md. It guides you through CLI steps to create, validate, and apply the change proposal, ensuring consistency and reducing manual drafting overhead.

Yes, you can use a plain text description to create project artifacts. The skill accepts a descriptive request as input and outputs ready-to-implement design and tasks files without requiring a strict naming format upfront.

Yes, you need the openspec CLI to manage and validate generated change proposals. The skill relies on the CLI to check dependencies, guide artifact creation, and apply the change in a reproducible way.

The best way to ensure consistency across design specs and task planning documents is to automate generation. This skill creates proposal.md, design.md, and tasks.md in a single workflow, preventing manual errors and maintaining format uniformity.

Manually drafting project workflow artifacts slows down implementation because it is error-prone and requires separate files for design, specs, and tasks. Automating the proposal process reduces manual overhead and outputs ready-to-implement plans instantly.