Post #4098907

@marick@mstdn.social I'm not sure the full definition of 'trails' as used in this context...but if it is metaphorically akin to weak depth first search, in the sense that there is a thought and we have a new thought, so we make a save point and start looking at the new thought and when we get to the bottom of that rabbithole, we revisit a previous checkpoint...somewhat like a conversation or narrative...then this is very nearly how I'm (I'd argue successfully) using Claude-Code now days. Claude-code keeps track of claude.md files at the user/project/session levels that contain instructions for the "agent" part of Claude. There is also memory.md files that contain instructions/facts at the user/project/session levels that are germane to that project context...there is also a roadmap/plan.md file that is basically the "trail" part where I start with a "goal", decompose the goal into subtasks, decompose those into stages/phases, etc...Often the process of working on a "task" results in modification to the .claude, memory.md, or the plan.md. When a (sub-)task is complete, work continues on the next task identified in that trail. (There is more to it for successful claude development, but that is the part relevant to trails.)