clikan VS todo.txt

This is awesome! Super appreciate the effort on this.

One challenge I've had is the file-based concept. And it losing "shape" quickly. I taken a few whacks at something different and have settled on a CLI-based kanban-y thing: https://github.com/kitplummer/clikan

But this lacks things like tags - which I appreciate as long as they are searchable in some form.

It would be awesome to have an option to sync to/from a text file in the todo.txt format. This is a plain text format for tasks which can be read by different apps on different platforms.

For this project: Make a todo.txt file in the root. Don't go overboard, just note the tasks as you realize them as "(B) Add Audio System". Break them down into components when you realize tasks will take more than one sit-down, "(A) Put AudioDefs into an array \n (B) Load each of the filedata into a stack". Personally, I use (A) for "This is on the schedule", (B) "Do this today", etc.

Another way is to use the todo.txt approach and add context tags like "@work" to the text of the task, and then filter the big Tasks list by searching for that context tag.

todo.txt on linux (format definition, tool -- available in most package repos also I think, though the name is not always the same!)

Privat mittlerweile nach Todo.txt-Aufbau https://github.com/todotxt/todo.txt/blob/master/description.svg

Actually, it's org-mode. But for the rest of us non-Emacs users, there's todo.txt:

https://github.com/todotxt/todo.txt

Otherwise, maybe go old school and use a todo.txt type workflow?