Cross-Functional Agent Collaboration
The Problem
In a real company, different departments need to share context. In a solo setup, you become the bottleneck relaying information between agents.
How It Works
Each agent knows who the others are and how to hand work to them directly. A shared TEAM.md file lists every agent, their role, ID, and Discord channel. When one agent discovers something relevant, they route to the right agent automatically.
The Prompts That Drive This
The routing logic lives in each agent's AUTONOMY.md. The handoff pattern is consistent: who sent this, what happened, what is needed, where to send the result.
Related Use Cases
Overnight Coding Team (Architect & Coders)
Shipping software alone is slow. Features that should take two hours take a day because of context switching and debugging loops.
Design & Frontend Engineering
You know what the UI should look like. Getting from mockup to production code means switching between design tools, a code editor, and a browser dozens of times per feature. Most of the time is spent translating, not building.
Follow for more workflows and honest breakdowns of what broke.
Follow on X