A bot "build room" that plans, builds and merges PRs through Claude Code
Published
How can AI replace being the go-between for coding agents?
- Replaces: being the go-between for coding agents: turning ideas into tickets, starting each coding session by hand, passing review notes back and merging pull requests one by one.
- What to connect: a Grok Bot group chat (room) with five bots.
- A Product Owner that picks tickets and merges, a single T3 bot that starts sessions, and a Strategy bot that answers planning questions.
- Reviewer and Tester bots are used only when the Claude plan hits its limit.
- Add T3 Code with T3 Connect on the coding computer and its MCP URL as a Grok Bot connector.
- Claude Code (Opus 5.5 on an existing Claude plan) writes all the code; GitHub Actions for CI.
- Planning uses Matt Pocock's /wayfinder, /grilling, /research, /to-spec and /to-tickets skills, with /statechart and /deslop on flows and code.
- One fresh session per ticket and another per review; merge only on review PASS, test PASS, green CI and no open threads.
- Decisions on architecture, money, accounts or legal go to the owner.
- Full access on the coding machine means a session can change anything there.
- Who it's for: solo developers and small teams who already pay for a coding plan and want bots to run the ticket-to-merge loop.
From the Morning Tokens issue of Nov 12, 2026