openspec-propose

You can generate a complete change proposal with design docs and task plans by describing the intended change, which automatically scaffolds proposal.md, design.md, and tasks.md in a single step to accelerate planning.

An OpenSpec change proposal is a structured set of artifacts that keeps design rationale and implementation tasks aligned. You need one when planning new features or fixes to ensure consistent documentation across engineering teams.

To scaffold project artifacts for a new feature in one step, describe the change you want to build. This generates the required proposal, design, and tasks files simultaneously, reducing manual coordination.

Yes, generating a design doc automatically creates a task plan. The scaffolding process outputs proposal.md, design.md, and tasks.md together, ensuring your implementation tasks remain perfectly aligned with your design rationale.

Yes, you can use this for engineering task planning to track dependencies. It satisfies the OpenSpec workflow by scaffolding the necessary artifacts and mapping out the implementation tasks required for your proposed changes.

The best way to plan software fixes without manual coordination is using an automated proposal scaffolding process. It generates design and task artifacts simultaneously, ensuring fast-forward planning and documentation consistency.