Huh - turns out this is quite a pointed description of something I think I already subconsciously tried to achieve for some time without being really able to define it.

I usually try to build quite extensive documentation and task trackers for every project I am attempting. Now that I read this article I think a lot of it is indeed the feeling of knowing what to do next immediately after an arbitrarily long break and preventing the feeling of being "finished" just because I completed one feature/subtask.

Certainly worth trying to optimize for what the article is describing - does anyone has experience with this in a more general fashion (writing is a very unique thing IMO) or regarding software projects?