openspec-propose

To generate change artifacts automatically, describe your feature or fix request and the tool scaffolds a complete change directory, producing proposal.md, design.md, and tasks.md files in dependency order for immediate implementation.

The OpenSpec CLI creates change packages by using status and instructions commands to fetch artifact dependencies, ordering the work, and only generating proposal, design, and tasks files when prerequisites are satisfied.

Yes, you can turn a brief product request into a full change directory by providing a short feature description, which triggers interactive clarification, scaffolding, and generation of ready-to-implement spec and task artifacts.

The best way to scaffold change proposals in dependency order is using an automated workflow that reads artifact prerequisites and only creates the proposal, design, and tasks files when their respective dependencies are met.

No, you do not need to manually coordinate proposal, design, and tasks files, because the automated dependency-aware workflow reads instructions, honors artifact dependencies, and reports progress for each created file.

Change proposal generation asks clarifying questions during the process to resolve unclear input, ensuring the automatically generated proposal, design, and tasks artifacts accurately reflect the intended feature or fix before implementation.