I know we can just use a tasklist.md or something similar to track and manage task flow, and this mostly works, however, I have seen boomerang and taskweaver and I imagine there are other solutions.

But ultimately, I think having this discrete task list locked in and managed as part of the work "flow" would be super helpful.

And a lil less jenky than packing it in my readme or other documentation.

Maintaining good documentation is now a breeze in relative terms; however, the utilization of this for contextual awareness, management, and process or workflow grounding is... well its janky af.

I think building this in more robustly, so that tasks can expand (discovered subtasks), and be kept as recorded completions or incomplete, etc to prevent loops or repeated task suggestions, would be exceedingly beneficial and helpful. Additionally, if a particular approach to a problem was attempted, instead of relying on my feeble human brain to remember all the details and nuances (which I do not always do perfectly) this embedded task list would have that evidence trail for me to reflect on most easily, rather than trying to remember all the details, reading through everything, checking docs, or scrolling through the chat history which includes a lot of noise in some cases. Because I got a lot of silly questions sometimes.

Happy to expand more, but I am pretty sure you guys are smart and know what I mean, or close to it, and have likely already been talking about this internally.

But TL;DR: I think some project management tooling baked in would go a really long way, especially in utilizing the capacity of the context potential on the new gen releases imho. It allows a project to essentially gain context organically in-between chats or sessions.

I could also use taskweaver or something. But I mean. Im here for the vibes. If there is a function I am just ignorant to, please alleviate me of my ignorance.