# Coordination Patterns Between Marketing Agents Across Platforms in Agency Agents

> Discover coordination patterns between marketing agents. The Agency Agents framework orchestrates synchronized cross-platform campaigns via a central hub and real-time analytics.

- Repository: [Michael Sitarzewski/agency-agents](https://github.com/msitarzewski/agency-agents)
- Tags: deep-dive
- Published: 2026-03-09

---

**The Agency Agents framework implements a NEXUS (Network of EXperts, Unified in Strategy) operating model that orchestrates marketing agents through a central hub, standardized handoff templates, and real-time analytics feedback loops to ensure synchronized cross-platform campaigns.**

The `msitarzewski/agency-agents` repository defines sophisticated **coordination patterns between marketing agents across platforms** using a multi-layered architecture. These patterns transform isolated AI specialists into a unified team capable of executing complex, synchronized marketing campaigns across social media, community forums, and digital storefronts.

## The NEXUS Operating Model

The framework’s coordination logic is defined in [`strategy/nexus-strategy.md`](https://github.com/msitarzewski/agency-agents/blob/main/strategy/nexus-strategy.md) and implemented through three architectural layers that govern how agents interact.

### Orchestration Hub

At the center of the coordination pattern sits the **Agents Orchestrator**, defined in [`strategy/coordination/agent-activation-prompts.md`](https://github.com/msitarzewski/agency-agents/blob/main/strategy/coordination/agent-activation-prompts.md). This hub activates agents, tracks handoffs, and enforces quality gates.

When a campaign initiates, the orchestrator spins up a **Social Media Strategist** as the campaign lead, then dispatches platform-specific agents—including the **Twitter Engager**, **TikTok Strategist**, **Instagram Curator**, and **Reddit Community Builder**—in parallel.

### Standardized Handoff Protocol

Every inter-agent transfer follows the **NEXUS Handoff Template** located in [`strategy/coordination/handoff-templates.md`](https://github.com/msitarzewski/agency-agents/blob/main/strategy/coordination/handoff-templates.md). This template carries full context—project metadata, dependencies, acceptance criteria, and evidence requirements—ensuring no knowledge is lost between agents.

When the **Content Creator** (defined in [`marketing/marketing-content-creator.md`](https://github.com/msitarzewski/agency-agents/blob/main/marketing/marketing-content-creator.md)) finishes a blog post, it hands the draft to the **Brand Guardian** (referenced via [`design/design-brand-guardian.md`](https://github.com/msitarzewski/agency-agents/blob/main/design/design-brand-guardian.md)) for brand-consistency review, then to each platform agent for adaptation.

### Feedback Loop and Analytics

After each platform delivers content, the **Analytics Reporter** (from [`support/support-analytics-reporter.md`](https://github.com/msitarzewski/agency-agents/blob/main/support/support-analytics-reporter.md)) collects performance data, feeding it back to the **Growth Hacker** and **Social Media Strategist** for real-time optimization. The loop closes via the **Evidence Collector**, which records screenshots and KPI snapshots.

During execution, the **Twitter Engager** posts a launch thread, the **Analytics Reporter** logs impressions and engagement, and the **Growth Hacker** reallocates ad budget based on observed click-through rates.

## Campaign Core Plus Platform Specialists Pattern

The [`strategy/runbooks/scenario-marketing-campaign.md`](https://github.com/msitarzewski/agency-agents/blob/main/strategy/runbooks/scenario-marketing-campaign.md) file explicitly encodes a three-tier coordination pattern that structures **coordination patterns between marketing agents across platforms**:

1. **Campaign Core**: Comprising the **Social Media Strategist**, **Content Creator**, **Growth Hacker**, **Brand Guardian**, and **Analytics Reporter**. This group defines strategy, creates assets, sets KPIs, and tracks results.

2. **Platform Specialists**: Including the **Twitter Engager**, **TikTok Strategist**, **Instagram Curator**, **Reddit Community Builder**, and **App Store Optimizer**. These agents receive core assets, adapt them to each channel’s format, and execute the launch.

3. **Support Agents**: Such as the **Trend Researcher**, **Experiment Tracker**, **Legal Compliance Checker**, and **Executive Summary Generator**. These provide market timing, A/B-testing infrastructure, compliance checks, and stakeholder reporting.

All agents communicate via the handoff document and the orchestrator’s status-reporting API, guaranteeing that each platform agent receives the **brand guidelines** from the Brand Guardian, the **content calendar** from the Social Media Strategist, and the **performance expectations** from the Growth Hacker and Analytics Reporter.

## Cross-Platform Synchronization Mechanisms

The framework implements four specific mechanisms to ensure agents remain synchronized across disparate platforms.

### Shared Content Calendar

A single markdown calendar generated by the **Social Media Strategist** drives publishing dates for every platform agent. In the runbook, `Day 1-2` shows the calendar creation step; each platform agent then references that same schedule to coordinate drops.

### Brand Consistency Checkpoints

The **Brand Guardian** reviews every piece before it reaches a platform agent. Checkpoints defined in the runbook under “Brand Consistency Checkpoints” prevent publication until sign-off is complete. The **Twitter Engager** cannot publish a thread until the Brand Guardian signs off on the “Content review before publishing” criterion.

### Analytics-Driven Optimization

Real-time dashboards from the **Analytics Reporter** inform the **Growth Hacker**, who adjusts spend or messaging across all platforms. In Week 2, if the **Growth Hacker** observes a dip in Twitter CTR, they reallocate budget to TikTok and update the **Platform Specialists** via a new handoff document.

### Experiment Tracker A/B Tests

The **Experiment Tracker** runs variations of copy or creative across platforms; results consolidate and feed back to the **Content Creator** for next-iteration content. When testing two headline versions on Reddit, the **Experiment Tracker** reports the winner to the **Content Creator** for future posts.

## Implementation Examples

Below are practical snippets demonstrating the coordination patterns in action.

### Handoff Document from Content Creator to Brand Guardian to Platform Agents

```yaml

# NEXUS Handoff Document (example)

metadata:
  from: Content Creator (Marketing)
  to: Brand Guardian (Marketing)
  phase: Phase 3 — Build & Iterate
  task_reference: CONTENT-001
  priority: High
  timestamp: 2026-03-09T12:00:00Z
context:
  project: "Spring-Launch-2026"
  current_state: "Blog post draft, email sequence, social copy ready"
  relevant_files:
    - path: marketing/marketing-content-creator.md
      description: "Core copy assets"
    - path: design/design-brand-guardian.md
      description: "Brand guidelines"
  dependencies: []
  constraints:
    - "All copy must stay under 280 characters for Twitter"
    - "Video length ≤ 60 seconds for TikTok"
deliverable_request:
  what_is_needed: "Brand-approved copy package for all platforms"
  acceptance_criteria:
    - "[ ] All copy matches tone & visual style"
    - "[ ] No regulatory language violations"
    - "[ ] Files exported in platform-specific formats"
  reference_materials:
    - https://github.com/msitarzewski/agency-agents/blob/main/design/design-brand-guardian.md
quality_expectations:
  must_pass: "Brand Guardian sign-off"
  evidence_required: "Signed handoff PDF + annotated copy files"
  handoff_to_next: "Twitter Engager, TikTok Strategist, Instagram Curator, Reddit Community Builder"

```

The file paths and links correspond to the real source files: [`marketing/marketing-content-creator.md`](https://github.com/msitarzewski/agency-agents/blob/main/marketing/marketing-content-creator.md) and [`design/design-brand-guardian.md`](https://github.com/msitarzewski/agency-agents/blob/main/design/design-brand-guardian.md).

### Activation Prompt for a Multi-Platform Campaign

```markdown
You are the Agents Orchestrator executing a NEXUS-Micro campaign for **Spring-Launch-2026**.

Mode: NEXUS-Micro → NEXUS-Sprint  
Agents:
- Social Media Strategist
- Content Creator
- Growth Hacker
- Brand Guardian
- Analytics Reporter
- Twitter Engager
- TikTok Strategist
- Instagram Curator
- Reddit Community Builder
- Trend Researcher
- Experiment Tracker

Pipeline steps:
1. Activate Social Media Strategist → define KPI-driven calendar.
2. Activate Content Creator → produce core assets.
3. Handoff → Brand Guardian → obtain sign-off (use handoff template).
4. Parallel activation of platform specialists → adapt assets.
5. Activate Analytics Reporter → start real-time tracking.
6. Growth Hacker ↔ Analytics Reporter → iterate spend & messaging.
7. Evidence Collector → capture screenshots for each platform post.

Report status after each phase using the NEXUS Pipeline Status Report format.

```

Running this prompt with the orchestrator spins up the exact coordination pattern, wiring all marketing agents together automatically.

## Key Coordination Files

| File | Role in Coordination | Link |
|------|---------------------|------|
| [`marketing/marketing-content-creator.md`](https://github.com/msitarzewski/agency-agents/blob/main/marketing/marketing-content-creator.md) | Core copy and content creation for all platforms | [Marketing Content Creator](https://github.com/msitarzewski/agency-agents/blob/main/marketing/marketing-content-creator.md) |
| [`marketing/marketing-twitter-engager.md`](https://github.com/msitarzewski/agency-agents/blob/main/marketing/marketing-twitter-engager.md) | Real-time Twitter/X engagement specialist | [Twitter Engager](https://github.com/msitarzewski/agency-agents/blob/main/marketing/marketing-twitter-engager.md) |
| [`marketing/marketing-tiktok-strategist.md`](https://github.com/msitarzewski/agency-agents/blob/main/marketing/marketing-tiktok-strategist.md) | TikTok short-form video strategist | [TikTok Strategist](https://github.com/msitarzewski/agency-agents/blob/main/marketing/marketing-tiktok-strategist.md) |
| [`marketing/marketing-instagram-curator.md`](https://github.com/msitarzewski/agency-agents/blob/main/marketing/marketing-instagram-curator.md) | Instagram visual storytelling | [Instagram Curator](https://github.com/msitarzewski/agency-agents/blob/main/marketing/marketing-instagram-curator.md) |
| [`marketing/marketing-reddit-community-builder.md`](https://github.com/msitarzewski/agency-agents/blob/main/marketing/marketing-reddit-community-builder.md) | Reddit community engagement | [Reddit Community Builder](https://github.com/msitarzewski/agency-agents/blob/main/marketing/marketing-reddit-community-builder.md) |
| [`strategy/runbooks/scenario-marketing-campaign.md`](https://github.com/msitarzewski/agency-agents/blob/main/strategy/runbooks/scenario-marketing-campaign.md) | End-to-end runbook encoding the "Campaign Core + Platform Specialists" pattern | [Marketing Campaign Runbook](https://github.com/msitarzewski/agency-agents/blob/main/strategy/runbooks/scenario-marketing-campaign.md) |
| [`strategy/coordination/agent-activation-prompts.md`](https://github.com/msitarzewski/agency-agents/blob/main/strategy/coordination/agent-activation-prompts.md) | Canonical activation prompts used by the Orchestrator | [Agent Activation Prompts](https://github.com/msitarzewski/agency-agents/blob/main/strategy/coordination/agent-activation-prompts.md) |
| [`strategy/coordination/handoff-templates.md`](https://github.com/msitarzewski/agency-agents/blob/main/strategy/coordination/handoff-templates.md) | Standard handoff document guaranteeing context continuity | [Handoff Templates](https://github.com/msitarzewski/agency-agents/blob/main/strategy/coordination/handoff-templates.md) |
| [`strategy/nexus-strategy.md`](https://github.com/msitarzewski/agency-agents/blob/main/strategy/nexus-strategy.md) | High-level matrix showing Marketing division agents and coordination scope | [NEXUS Strategy](https://github.com/msitarzewski/agency-agents/blob/main/strategy/nexus-strategy.md) |
| [`support/support-analytics-reporter.md`](https://github.com/msitarzewski/agency-agents/blob/main/support/support-analytics-reporter.md) | Collects cross-platform performance data for feedback loops | [Analytics Reporter](https://github.com/msitarzewski/agency-agents/blob/main/support/support-analytics-reporter.md) |

These files illustrate how marketing agents share context, synchronize schedules, enforce brand consistency, and close feedback loops through analytics.

## Summary

- The **NEXUS** (Network of EXperts, Unified in Strategy) model provides the architectural foundation for **coordination patterns between marketing agents across platforms**, replacing isolated execution with orchestrated teamwork.
- Three coordination layers—**Orchestration Hub**, **Standardized Handoff Protocol**, and **Feedback Loop & Analytics**—ensure that agents like the **Twitter Engager**, **TikTok Strategist**, and **Instagram Curator** operate from shared context.
- The **Campaign Core + Platform Specialists** pattern defined in [`strategy/runbooks/scenario-marketing-campaign.md`](https://github.com/msitarzewski/agency-agents/blob/main/strategy/runbooks/scenario-marketing-campaign.md) structures workflows so that strategy, content, and analytics agents form a stable core while platform specialists execute channel-specific adaptations.
- **Cross-platform synchronization** relies on shared content calendars, brand consistency checkpoints enforced by the **Brand Guardian**, analytics-driven optimization via the **Analytics Reporter**, and A/B testing managed by the **Experiment Tracker**.

## Frequently Asked Questions

### How does the Agency Agents framework prevent marketing agents from working in silos?

The framework prevents silos through the **NEXUS Handoff Template** defined in [`strategy/coordination/handoff-templates.md`](https://github.com/msitarzewski/agency-agents/blob/main/strategy/coordination/handoff-templates.md). Every agent transfer includes full project metadata, dependencies, acceptance criteria, and evidence requirements. Additionally, the **Agents Orchestrator** maintains a centralized status-reporting API that ensures all platform specialists see updates from the Campaign Core agents in real time.

### What is the role of the Brand Guardian in cross-platform coordination?

The **Brand Guardian** (referenced in [`design/design-brand-guardian.md`](https://github.com/msitarzewski/agency-agents/blob/main/design/design-brand-guardian.md)) acts as a mandatory checkpoint in the coordination pipeline. Before any platform agent—such as the **Twitter Engager** or **TikTok Strategist**—can publish content, the Brand Guardian must sign off on brand consistency. This enforcement happens through the handoff document’s `quality_expectations` field, which blocks progression until `must_pass: "Brand Guardian sign-off"` is satisfied.

### How does the framework handle real-time optimization across different marketing channels?

Real-time optimization operates through a closed feedback loop involving the **Analytics Reporter** ([`support/support-analytics-reporter.md`](https://github.com/msitarzewski/agency-agents/blob/main/support/support-analytics-reporter.md)) and the **Growth Hacker**. The Analytics Reporter collects performance data from all platform agents—impressions, engagement rates, and click-through rates—and feeds this to the Growth Hacker. The Growth Hacker then adjusts budget allocation or messaging strategy across platforms (for example, shifting spend from Twitter to TikTok based on CTR data) and issues new handoff documents to update the **Platform Specialists**.

### Can the coordination patterns scale from small campaigns to full marketing sprints?

Yes, the framework explicitly supports scaling through mode transitions defined in the activation prompts. A campaign can start as **NEXUS-Micro** (minimal viable coordination) and escalate to **NEXUS-Sprint** (full orchestration) as complexity increases. The [`strategy/runbooks/scenario-marketing-campaign.md`](https://github.com/msitarzewski/agency-agents/blob/main/strategy/runbooks/scenario-marketing-campaign.md) runbook outlines this scaling path, allowing the Campaign Core to add Platform Specialists and Support Agents (like the **Experiment Tracker** or **Legal Compliance Checker**) dynamically as campaign requirements grow.