Original Reddit post

I've been using coding agents in lanes instead of one chat that does the whole job. A lead figures out the work and files a GitHub issue. Then separate runs do implementation, QA, review, and CI. There's a telemetry lane for when you don't know what broke or a path just died. floor starts the next lane. Nobody implements, reviews, and merges in the same session. When a lane finishes, it writes started , done , blocked , or failed . The next process reads that before it does anything. That's SQLite on this machine, plus a GitHub comment so the trail isn't stuck on one laptop. The PR can come from an agent. I still merge it. The CLI is a plug. Same rules on Claude, Codex, and Grok. I've been running this on my own repos and gave it to a few mates. One of them liked how it kicks off the next lane, which is what made me put the repo up. If you already live in coding agents, I'd like to see it on a messy repo, or hear how you'd cut the lanes differently. https://github.com/Kripu77/software-factory submitted by /u/NewAmbition8911

Originally posted by u/NewAmbition8911 on r/ClaudeCode