Marketing team in Slack: one lead, five specialists. Blog drafts in Notion, posts in Typefully, campaigns in Resend, on approval.
Most "AI team" demos are one model wearing five hats. This template is an actual org: a lead agent you brief in Slack and five specialists it delegates to, each with its own instructions, skills, and tools. Tell the lead "we're launching Thursday, draft the announcement posts" and it reads your brand context, briefs the social media coordinator, and comes back with drafts sitting in your Typefully queue. Blog posts land in Notion, email campaigns in Resend, and nothing irreversible ships without an approve button. Built on eve, Vercel's agent framework.
Five specialists, each with a distinct job and a distinct deliverable:
Some work routes through two of them, in order. A newsletter goes to the content marketer for the writing, then to the email specialist for the inbox adaptation and the send, so it gets both crafts instead of a compromise between them.
Multi-agent setups usually fail on shared state: everyone reads everything, context drifts, and agents contradict each other. This template makes four deliberate architecture calls instead:
One shared document, one owner. The team's only shared state is the brand context: a short document describing what your product is, who it's for, and what you claim about it. The product marketer owns it; every other specialist reads it fresh at the start of a task. No agent inherits another's conversation.
Self-contained briefs. Specialists start each task in a clean session, so the lead packs everything into the brief: the ask, the relevant brand context quoted rather than referenced, your preferences stated as constraints, and the destination for the deliverable. The lead never writes deliverables itself; it routes, sequences, and hands back.
Delegation goes one level deep. Specialists research and self-edit against a written rubric rather than spawning further agents, so a request never disappears into a recursion you can't audit.
Big documents travel by reference. A long draft passes between specialists as an artifact id in private Blob storage, not as text through the lead's context, so a 5,000-word audit doesn't clog the conversation that's coordinating it.
Drafting is friction-free everywhere. The irreversible actions all pause for an approve or deny button: sends and deletes in Resend, deletes and scheduled publishes in Typefully, page moves in Notion. Two boundaries go further. The email specialist sees only 47 of Resend's roughly 85 tools, an allow-list covering campaigns, lists, and diagnostics, so API keys, webhooks, and domain writes are unreachable rather than merely gated. And Resend sends run on user-scoped OAuth through Vercel Connect, so every campaign is attributed to the person who approved it, not to a bot account.
Click Deploy and Vercel provisions the Slack, Notion, and Resend connectors, a Blob store, and prompts for your Typefully API key. One prerequisite before your first campaign: verify a sending domain and create a segment in the Resend dashboard, since the agent picks from your verified domains but can't do DNS for you. In a fresh Slack conversation the bot pins four starter prompts, one per craft: sharpen positioning, write a blog post, draft social posts, review a page's SEO.
Working with an AI coding agent like Claude Code or Cursor? Point it at the setup guide and let it drive:
The roster is a directory. Add a folder under agent/subagents/ and the lead picks the new specialist up from its description; that description is all the routing sees. Each specialist's craft lives in its own instructions.md and skills, voice rules live in per-surface banned-words.json files checked by a lint tool, and approval gates are tool lists in each connection file. The repo ships a full customization walkthrough with recipes for adding a specialist, skill, tool, or connection.
Specialists don't have to live in this repo either. eve's remote agents let the lead delegate to an agent in its own deployment over an OIDC-authenticated call, with no shared secret. Useful when a specialist needs credentials you'd rather isolate, like ad platform access, or when one of the standalone eve agents (the Content Agent, Typefully Agent, or Sanity Copilot) should join the team as-is.
