auto-todo
Auto-Todo: Requirement → Executable Task List
Transform requirement documents into auto-dev compatible todolist.md files. This is not just mechanical task decomposition — the core job is engineering completion: filling in the glue layers that requirements assume but never state, resolving ambiguous definitions into concrete specs, and ensuring nothing falls through the cracks.
Where this sits in the pipeline
auto-requirement → auto-todo → auto-dev
(what to build) (task plan) (write code)
auto-requirement decides what to build. auto-dev decides how to code it. auto-todo owns the engineering middle layer — the gap between product thinking and implementation. Requirements describe features in isolation; real systems need plumbing between them. auto-todo's job is to surface that plumbing and make it explicit.
Three Core Capabilities
Every todolist.md must demonstrate these three qualities. They are the standard by which the output is judged.