topydo

**Judgment:** Strong, feature-complete todo.txt task manager suitable for power users and text-based workflows, with some usability and data-safety caveats. **What it’s good for** - Managing complex todo.txt setups with priorities, projects, contexts, dependencies, recurrence, and rich date logic. - Fast querying and reviewing of tasks using filters, sorting, grouping, and custom output formats (including JSON). - Users who value plain-text portability and want to keep tasks in `todo.txt` / `done.txt` under version control. **Key risks / limitations** - **Destructive operations on user data:** Commands like `del`, `archive`, `sort`, and bulk `do -e` modify or remove tasks; incorrect use or mis-specified filters can cause unwanted changes. Revert support helps but may not cover all scenarios. - **Config and path sensitivity:** Misconfigured `filename` / `archive_filename` may lead to operating on the wrong files or confusing behavior. - **Learning curve:** The rich CLI syntax (filters, tags, dependency notation, relative dates, custom formats) can be complex for non-technical users; it is best suited to users comfortable with CLI concepts. **Recommended scenarios** - Users explicitly mentioning todo.txt, topydo, or text-based/CLI task management and wanting advanced automation or filtering. - Environments where tasks need to be scriptable, version-controlled, or shared as plain text (e.g., developers’ workflows). - Assistant-driven flows where the AI can reliably construct precise topydo commands for listing, tagging, postponing, or completing tasks, while being cautious with bulk-modifying or deleting commands.