openspec-propose

Generating change proposals requires creating proposal.md, design.md, and tasks.md based on artifact dependencies. This workflow queries instructions, reads completed dependencies for context, and iterates until all implementation-required artifacts are done.

Creating proposal.md, design.md, and tasks.md in dependency order involves querying artifact instructions and reading completed dependencies for context. The workflow iterates through each file until all implementation-required artifacts are generated and ready for review.

Yes, the openspec CLI is required to scaffold changes and retrieve artifact instructions. It provides the necessary structure to generate proposal.md, design.md, and tasks.md files accurately based on project dependencies.

The best way to prepare implementation tasks is using an interactive clarification and validation workflow that generates design specs and tasks.md. It verifies files exist before proceeding, ensuring reproducible change proposals for developer and product teams.

Yes, the change proposal workflow validates files and prompts for clarification. It checks that files exist before proceeding and asks for input when instructions are unclear, ensuring artifact generation remains accurate and reproducible.

Manual change proposal creation fails because rapidly generating well-structured design specs and tasks is time-consuming and error-prone. Automating the end-to-end creation of these artifacts ensures teams move from idea to implementation readiness in one consistent flow.