The 300k line monorepo with 3-6 CLI agents running simultaneously across git worktrees is an interesting production deployment of multi-agent coding. Most discussions are about single-agent workflows; the coordination problems at multi-agent scale are different and less explored. The key insight in your description is the worktree-per-agent isolation pattern. Without that isolation, agents would interfere with each o…
the harder problem you're pointing at is agent-to-agent coordination. i don't try to solve that at the orchestration layer. i keep it simple: one agent per feature, and they don't touch each other's worktrees. when feature A needs something from feature B, i merge feature B first. boring, but it doesn't blow up
the ADR / architectural governance point from agilevibecoding.org is interesting though -- have you seen teams actually ship something like that in practice? or is it mostly theoretical at this scale?