Slack Deployment: Unified Agent Structure
Deployment: Unified Agent Structure (Workers & Workflows)
📎 Demo: [Add demo link when recorded]
What this is
Reorganized all our GTM agents so you can actually find and use them. Before: agents scattered across 4+ different folders, no clear way to know which agent to use or how to chain them together. Now: everything in one place (gtm/agents/workers/) organized by what they do, plus workflows showing how to run multiple agents in sequence for complex tasks.
Why this matters
• No more “where’s that agent?” — Everything lives in gtm/agents/workers/ organized by function. Need content? Check content-generation/. Need outreach? Check outreach/.
• See how agents work together — We documented common workflows (Campaign Launch, Event to Meeting) so you know which agents to run in what order. Example: Launching a campaign? Run Brief → Copy → Posts → Sequences → Done. No more guessing.
• Agents learn from your usage — All agents now use the same feedback system, so they improve over time based on how you actually use them.
How this changes how you work
• Before: “I need to create a campaign brief… where do I go? Is it in campaign-launch/ or agents/? And then what agent do I run next for the copy?”
• After: Go to gtm/agents/README.md → See Campaign Launch workflow → Follow the steps: Brief → Copy → Posts → Sequences. Everything is documented and in one place.
• Before: Each agent felt isolated. No clear way to see how they connect.
• After: Workflows show the full picture. Want to convert event attendees to meetings? Follow Event to Meeting workflow: ICP Analysis → Follow-Up → Sequences.
Where it lives
In brainforge-vault (PR ready):
• Start here: gtm/agents/README.md
• All workers: gtm/agents/workers/ (12 workers organized by category)
• Workflows: gtm/agents/workflows/ (how to chain workers together)
• Complete list: gtm/agents/AGENT_REGISTRY.md
What this enables
• Better discoverability — All 12 workers in one place, organized by function. Easy to find what you need.
• Clear workflows — Documented how to chain workers together for complex tasks (Campaign Launch, Event to Meeting, Deployment).
• Continuous improvement — All workers wired to feedback loop, so they learn and improve based on how you actually use them.
• Future-ready — Structure supports multi-agent orchestration, so we can automate complex workflows as we scale.
Invite critical feedback: What’s broken, missing, or annoying? What would make you actually use this (or use it more)? Reply in thread or DM me.