openspec-propose

Automating change proposal documentation involves generating proposal.md, design.md, and tasks.md files from a user-provided feature description. This workflow ensures structured planning and consistency for software teams without manual writing.

An automated change proposal artifact includes proposal.md, design.md, and tasks.md files generated in a single step. These provide ready-to-implement documentation, design specifications, and task breakdowns based on your feature description.

To create a feature proposal with task breakdowns quickly, describe the desired change and let the system automatically generate the relevant documentation. You receive ready-to-implement task lists and specifications in a single step.

No external dependencies are required to generate project planning artifacts. You simply input your change description, and the automation workflow handles producing the design and task planning documents directly.

The best way to ensure consistency in software change documentation is using an automated workflow that generates all artifacts from a single description. This enforces a unified structure across proposals, designs, and task lists.