推文

I went HAM on git worktrees when I learned they were a thing like 6 months ago but slowly drifted back to single branch flows. It's just way easier to manage and far less repeat/conflicting work. But how do you make sure multiple agents don't collide? The flow is simple: You need proper planning. Measure twice cut once has never been more true. After the plan is created, I prompt the model if it's 100% clear on what to do, and if not to surface non obvious questions + edge cases we haven't yet covered. Now with a SOLID plan, I turn it into a directed graph of tasks where they know the clear order of operations. The task graph is then fed into a swarm of tmux sessions running [insert your favorite harness here] by a top level agent, lets call it the "ring leader" The agent sessions collaborate via file reservations and their own agent mail messaging system. This ensures no edits are conflicting and duplicate work is not done. The top level ring leader agent just sits there on a cron, checking in to the sessions every ~5 minutes to nudge them to pickup unblocked tasks from the graph if there are any until all the work is done. Then when its all done, I prompt for a summary of work completed and a QA plan for me or other agent to verify. This is like the "ralph loop" but on galactic steroids. It gets work done would have taken several weeks a year ago to get done in a ~2 hour session. If this all sounds too hard to manage, I thought so too. But then I stumbled across what @doodlestein was doing thru one of @johnlindquist's AI workshops. Then Jeffrey released his skills https://t.co/aHly1cpc2A and holy cow everything I just mentioned above unlocked.