ngl this actually makes a lot of sense. i've been running into the same “context rot” problem with copilot / claude sessions… you spend like an hour discussing architecture with the agent and a few days later the whole reasoning is basically gone. starting from scratch again... the idea of keeping the planning conversation as plain markdown in the repo is kinda neat. boring in a good way. no database, no hidden state, just files you can diff and commit. feels very git-native. also like the plan → todo → implement separation. forcing the agent to write the plan first probably saves a lot of token-wasting thrashing. curious though — how messy do those task md files get after a while? i can imagine long agent conversations turning them into pretty big logs.