
How I built a 9-agent team where my agents actually talk to each other
I've been running Claude Code for 6 months, shipping my product and running content/launch ops for it. The thing that kept breaking wasn't the agents themselves. It was me. Every handoff between research and write and code and review was me copy pasting context between sessions. I was the dispatcher and context holder for my own AI team
Tried gstack first. The roles are great but I'm still the one cycling through slash commands. /office-hours → /plan-eng-review → /review → /ship. Good output, but I'm orchestrating every step
Spent a weekend porting my workflow over. Here's the lineup:
Engineering (4 agents)
- arch: owns architectural decisions. Reviews proposed changes before code starts. Soul: "senior staff engineer, asks 'what breaks at 10x' before approving anything
- backend: owns /api, /services. Implements after arch greenlights
- frontend: owns /web. Picks up from backend when API contracts are stable
- review: reads every PR before I do. Catches the lazy stuff so I only review substantive changes
Growth/Content (5 agents)
- research: uses ahrefs MCP to analyse keywords/opportunities/market and hands off to strategist
- strategist: reads research, writes campaign briefs. Doesn't write copy, only frames the angle
- writer: drafts blog posts given by strategist and avoid mistakes using the memory from the edits I have previously suggested
- editor: fact-checks and rewrites for voice. Brand style guide lives in its memory
- SEO: takes finalized copy, adds metadata, structures for the blog
The handoff that changed everything: when backend ships an API change, it messages frontend directly. When writer finishes a draft, it pings editor. When arch blocks a change, it explains why in team chat and backend adjusts. I see the conversation happen on a canvas
What actually works
- Each agent has a persistent Soul + Purpose + Memory. The editor knows our voice after 3 weeks. The arch agent remembers what we decided about caching last month
- Auto-captured Knowledge Base. The strategist remembers the pattern of our best-performing posts and create briefings accordingly
Happy to share the Soul/Purpose docs if anyone wants them, they took the longest to dial in