What I am talking about is really very different from the Pomodoro method. That method uses 25-minute sessions, while I am talking about micro-tasks of 2 to 5 minutes printed on receipt tickets.
As for todo.txt, I mentioned in the article that this kind of tool with a hierarchy does not work for me at all, given the massive number of tasks I have. And I proposed a more interesting and truly innovative solution in response to that :)
Instead made a single issue with a table and each row having an emoji, item title, and when complete link to the fix. As new items were identified I added a row with emoji for 'not started'. Had emoji's were 'under construction', 'already done above', 'not needed', etc. This snowballed with me completing one item per day over 30 days until it was all done. I'm called it EDD Emoji-Driven-Development.
In Sleek (todo.txt for linux) I can have multiple txt with multiple context inside.
On the other hand, I don't think pomodoros are strictly 25 minute sessions. I can setup any structure in my pomodoro app of choice Solanum and chain sessions.