marketing-team-eve-template: Five Specialists, One Lead, Real Deliverables

What the Template Solves for a Small Marketing Team

A common pattern with AI writing tools is that the same assistant drafts a blog post and a tweet in the same session, with no clear separation of concerns and no persistent record of what the brand claims. Every new task starts from a blank slate.

This template takes a different approach. A lead agent holds the brand context and assigns work to one of five specialists: product-marketer, content-marketer, social-media-coordinator, seo, and email. Each specialist has a defined output format and a defined destination. The content marketer writes long-form copy and delivers a Notion page link. The social media coordinator handles short-form posts for X, LinkedIn, Threads, Bluesky, and Mastodon, queuing drafts in Typefully. The email specialist builds and sends campaigns in Resend.

The README describes the workflow with a concrete example: a user asks the lead to draft launch announcement posts, the lead checks the brand context, briefs the social media coordinator, and hands back three drafts in Typefully, one each for X, LinkedIn, and Bluesky, none scheduled yet.

The target is a team that is already using Notion for long-form content, Typefully for social media scheduling, and Resend for email campaigns, and wants a Slack-based interface to coordinate those tools through an AI lead.

The Brand Context Document and Why It Has One Owner

The five specialists share no conversation history with each other. Each starts fresh on every task, with the lead's brief as its only input. The only shared state in the system is the brand context document: a short file describing what the product is, who it is for, and what the team claims about it.

The product marketer owns this document exclusively. Every other specialist reads it at the start of a task. The README is explicit about the design reason: a document with a single owner avoids the consistency problems that come from multiple agents writing to the same state. Newsletters illustrate how the boundary works in practice. The content marketer writes the prose. The email specialist then adapts that prose for the inbox and sends it through Resend. Two passes from two specialists, with no shared session.

Briefs are self-contained by design. The lead writes a brief that carries everything the specialist needs, so the specialist never needs to ask the lead a follow-up question mid-task. The README notes that delegation goes one level deep: specialists do their own research and editing rather than spawning sub-agents.

Deploying and Running Locally

The README describes a one-click deploy that provisions all connectors:

vercel link
vercel env pull
pnpm dev          # then run /model once in the TUI to link a provider

The one-click deploy sets up four things automatically: a Notion connector, a Resend connector, a Slack connector, and a Vercel Blob store. It prompts for the Typefully API key during setup. Environment variables NOTION_CONNECTOR, RESEND_CONNECTOR, SLACK_CONNECTOR, and TYPEFULLY_API_KEY are all populated by the deploy flow.

For local development, four commands cover most workflows:

pnpm dev          # eve dev TUI
pnpm validate     # lint, typecheck, and discovery diagnostics
pnpm check        # Ultracite check
npx eve info      # print every discovered tool, skill, connection, and subagent

The project requires Node 24.x and uses TypeScript in strict ESM mode. The full dependency list is in package.json; the eve framework is at version ^0.39.3. The Ultracite preset, built on Biome, handles linting and formatting.

Before running the first email campaign, the README calls out a manual step: verify a sending domain and create at least one segment in the Resend dashboard. The email agent can see verified domains and segments but cannot create a domain or verify DNS records.

What the Approval Gate Blocks

The README lists the actions that pause for your approval before proceeding: sends and deletes in Resend, deletes and scheduled publishes in Typefully, and page moves in Notion. The approval prompt surfaces as a button in Slack or in the terminal.

Drafting is friction-free. Creating a Notion draft, queuing a post as a draft in Typefully, or building a Resend campaign without sending it all proceed without interruption. The gate applies only at the point where the action becomes irreversible.

The email specialist also operates with a reduced tool surface. The README notes it can only see 47 of Resend's roughly 85 tools, leaving account administration out of reach. This is a deliberate scope limit, not a bug in the wiring.

Limitations of the Template

The template is tied to three specific destinations: Notion for long-form, Typefully for social, and Resend for email. Teams on different stacks must fork the repository and replace the MCP connectors. The full customization guidance is in docs/CUSTOMIZING.md.

The lead handles coordination but does not write deliverables. If the required output is something none of the five specialists cover, the team must add a specialist. The README mentions that the agent auto-updates as you edit configuration files, but adding a new specialist requires more than an edit to an existing file.

The brand context document is the only shared state. There is no mechanism for specialists to share observations between tasks. If the SEO specialist discovers something that should update the content marketer's understanding, that information reaches them only if the product marketer updates the brand context document manually.

The project has no GitHub releases. The last push was on 2026-08-20. There is no changelog file in the repository.

Compared to Using a Single AI Assistant Directly

Using a single AI assistant to draft a blog post, write social media copy, and compose an email in the same session works and requires no setup. The trade-off is that each task needs a full brief, the brand context is only as consistent as the prompt you write, and the output lands wherever you paste it: there is no automatic delivery to Notion, no Typefully queue, no Resend campaign.

This template trades setup time and provider costs for consistent brand context and automated delivery. The five-specialist model means each role has a narrow task and a fixed output destination. The cost is that you need active accounts and API keys for Notion, Typefully, Resend, and Slack before anything runs. The value is that once those are in place, routing a launch to the right specialist takes one line in Slack.

Editorial conclusion

Teams already using Notion, Typefully, and Resend will get the most value here: the template wires up those connectors with a one-click deploy and gives each specialist a clear scope. Teams on different publishing stacks will need to fork and rewire the connectors, which means reading docs/CUSTOMIZING.md and replacing the relevant MCP integrations. Before deploying, verify a sending domain in the Resend dashboard: the email agent can see existing verified domains but cannot create or verify one.

Frequently asked questions

Official sources

1. Issues
2. License: MIT
3. Project website
4. README
5. vercel-labs/marketing-team-eve-template on GitHub