> But GitHub (and most other engineering tracking tools) are meant for relatively clearly defined tasks I am not sure that's true. They are meant to avoid the

> But GitHub (and most other engineering tracking tools) are meant for relatively clearly defined tasks I am not sure that's true. They are meant to avoid the need for status meetings by providing more realtime feedback of what is and isn't happening to other people who benefit from knowing where things are at. As long as all interested parties understand the overall intent of the ticket, to know what it being closed means, it doesn't have to be well defined. If what you want to accomplish is so abstract that you can't even reach a shared understanding with others, they won't need to keep track of your status in the first place (what would they be keeping track of?), so that case is moot.