Hi HN, author here.<p>Like a lot of people, I found that using AI coding tools doubled my PR volume but created a new problem I call 'AI sprawl.' The agents act like interns with amnesia—they write good isolated code but constantly violate established architectural decisions, turning senior engineers into full-time PR reviewers.<p>I wrote this post detailing a 5-phase pipeline I built to fix this. The core mechanics rely on using git worktree to safely run up to 5 agents in parallel, and a review loop that forces agents to validate their diffs against our Architecture Decision Records (ADRs) before a human ever sees the PR.<p>The biggest win has been having AI automatically reject bad linting suggestions by citing our ADRs as the ultimate source of truth.<p>I'd love to hear how other teams are handling the review bottleneck as AI accelerates code generation, or any critiques on the workflow. Happy to answer any questions!