A plan in a document is a plan. The same plan as fifteen dated tasks with owners is work that happens.
Self-contained is the rule that matters
A task titled follow up on the segmentation point is not a task, it is a bookmark into a document somebody has to find and re-read. By the time that happens the plan has moved on and the context is gone.
So each task carries what it needs: what is being asked for, why, and what done looks like. It costs more to write and it is the difference between a task list that gets worked and one that gets archived.
Lanes rather than dates alone
Dates say when. Lanes say what happens when the week goes wrong, which it does. Main priority survives a bad week; second priority is what slips. Making that explicit up front is more honest than assigning fifteen tasks the same due date and discovering the ordering by attrition.
Draft by default
The output is a draft for a person to create, unless you explicitly ask it to write directly. Bulk task creation is easy to do and tedious to undo.
Runs well with
Skills compound. These are the ones we usually install alongside it.