GTM Agents: Workers & Workflows
Purpose: Unified system for all GTM agents (workers) and multi-agent workflows
Status: Active - All workers wired to feedback loop
Last Updated: 2026-02-05
🚀 Quick Start
New here? Start with:
- Architecture - Structure design (5 min read)
- Agent Registry - Complete worker inventory
- Pick a workflow: Campaign Launch or Event to Meeting
Want to run a worker?
- Find it in Agent Registry
- Read the worker’s
PRD.mdfor inputs/outputs - Run it → System prompts for feedback → Logs run → Analyzes patterns
📂 Structure
gtm/agents/
├── README.md # This file (overview)
├── ARCHITECTURE.md # Structure design
├── AGENT_REGISTRY.md # Complete worker inventory
│
├── workers/ # Individual workers (specialized jobs)
│ ├── content-generation/ # Copy, posts, deployment messages
│ ├── campaign-planning/ # Briefs, sequences
│ ├── outreach/ # Follow-ups, LinkedIn, partnerships
│ ├── analysis/ # ICP analysis, metrics
│ └── operations/ # Ticket creation
│
├── workflows/ # Multi-worker coordination
│ ├── campaign-launch-workflow.md
│ ├── event-to-meeting-workflow.md
│ └── deployment-workflow.md
│
├── shared/ # Shared infrastructure
│ ├── feedback-loop/ # Feedback system, run logs
│ ├── context-graph/ # Process knowledge
│ └── patterns/ # Learned patterns
│
└── examples/ # Example runs/outputs
🎯 Workers (Individual Agents)
Each worker is a specialized job that does one thing well. See Agent Registry for complete list.
Content Generation
- Design-Ready Copy - Marketing collateral (one-pagers, 2-pagers)
- Campaign Post - LinkedIn posts via CC content system
- Slack Deployment - Deployment win messages
Campaign Planning
- Campaign Brief Intake - Execution-ready campaign briefs
- Message Sequence - Multi-step outreach sequences
Outreach
- Event Follow-Up - Post-event sequences
- LinkedIn Sequence - LinkedIn-specific sequences
- Ticket Event Follow-Up - Follow-up automation
- VP Partnerships - Partnership outreach
Analysis
- ICP Analysis - Attendee list analysis
- Metrics Teardown - Metrics/KPI analysis
Operations
- Ticket Creation - Linear tickets from requests
🔄 Workflows (Multi-Worker Coordination)
Workflows orchestrate multiple workers to complete complex tasks:
Campaign Launch Workflow
Workers: Brief Intake → Design-Ready Copy → Campaign Post → Message Sequence → Slack Deployment
Input: Campaign idea
Output: Complete campaign ready to launch
See workflow →
Event to Meeting Workflow
Workers: ICP Analysis → Event Follow-Up → Message Sequence
Input: Event attendee list
Output: Prioritized sequences ready to send
See workflow →
Deployment Workflow
Workers: [Any Worker] → Slack Deployment → Feedback Loop
Input: New agent/tool deployed
Output: Team announcement + feedback logged
See workflow →
🔁 Feedback Loop System
Every worker run:
- Worker runs → Generates output
- System prompts → Structured feedback (2-3 min)
- Auto-log → Run logged to
shared/feedback-loop/RUN_LOG.md - Pattern analysis → “Thinking → summary” approach
- Impact summary → Time saved, quality trends, knowledge impact
- PR suggestions → When patterns reach MEDIUM confidence
See: Feedback Loop System
📊 Context Graph
The feedback loop builds a context graph that captures:
- Entities: Workers, workflows, outputs, patterns
- Actions/Traces: Who ran what, when, with what outcomes
- Process Patterns: How work actually gets done (not just what exists)
➕ Adding a New Worker
- Create worker directory:
workers/[category]/[worker-name]/ - Create PRD.md: Define inputs, outputs, rules
- Create feedback-prompt.md: Copy from similar worker
- Add to registry: Update
AGENT_REGISTRY.md - First run: Prompt for feedback → log → analyze patterns
🔗 Related
- Architecture - Structure design
- Agent Registry - Complete inventory
- Feedback Loop - How feedback works
- Run Log - All runs logged here
- Patterns - Learned patterns
Status: All workers wired to feedback loop. System ready for multi-worker workflows.