Any todo list that doesn't account for dependency tasks is exclusively limited to short term planning (i.e. days not weeks). After skimming the spec, I don't think dependency tasks are accounted for?
For example, say this is my (out of order) to-do list:
- [ ] Mix ingredients
- [ ] Eat cake
- [ ] Bake a cake
- [ ] Find cake pan
These tasks need to be done in a specific order, but reading the list top to bottom doesn't make sense.
So let's denote dependencies with indentation:
- [ ] Eat cake
- [ ] Bake a cake
- [ ] Find cake pan
- [ ] Mix ingredients
By specifying order through indentation, we've now created a DAG that orders and contextualizes tasks; with the most actionable tasks having the largest indentation. This is how I organize my plaintext to-do files, but afaict no todo list software is able to handle large task trees gracefully- with the exception of grit, which is more of an experiment (but the readme is incredibly well written and describes the DAG problem to a tee).
IMHO, you are mixing TODO lists and task management/planning software. No, I don't know a good task manager or business process manager for command line. Instead, I created a simpler TODO list manager, called `td`[0], which supports flat TODO lists only, and use directories and command-line generators to manage todo's. `td` prints top item only, by default, leaving little room for procrastination. I'm keeping one `TODO.md` file per project instead of one large TODO file for all todo's.
For example, say this is my (out of order) to-do list:
- [ ] Mix ingredients
- [ ] Eat cake
- [ ] Bake a cake
- [ ] Find cake pan
These tasks need to be done in a specific order, but reading the list top to bottom doesn't make sense.
So let's denote dependencies with indentation:
- [ ] Eat cake
By specifying order through indentation, we've now created a DAG that orders and contextualizes tasks; with the most actionable tasks having the largest indentation. This is how I organize my plaintext to-do files, but afaict no todo list software is able to handle large task trees gracefully- with the exception of grit, which is more of an experiment (but the readme is incredibly well written and describes the DAG problem to a tee).https://github.com/climech/grit
Does anyone know if org-mode handles complex task trees gracefully? All the examples I've found online were trivial (i.e. one task deep)