AGENT_REGISTRY

Agent Registry: All Workers in brainforge-vault

Purpose: Complete inventory of all workers (agents) that are wired to the automated feedback loop system. Every worker run should prompt for feedback, log runs, and analyze patterns.
Related: Architecture, Feedback Loop, Run Log, Patterns

---

Workers by Category

Content Generation Workers

Worker Name	Location	Status	Feedback Prompt
Design-Ready Copy	workers/content-generation/design-ready-copy/	✅ Active	feedback-prompt.md
Campaign Post	workers/content-generation/campaign-post/	✅ Active	feedback-prompt.md
Slack Deployment	workers/content-generation/slack-deployment/	✅ Active	feedback-prompt.md

Campaign Planning Workers

Worker Name	Location	Status	Feedback Prompt
Campaign Brief Intake	workers/campaign-planning/campaign-brief-intake/	✅ Active	feedback-prompt.md
Message Sequence	workers/campaign-planning/message-sequence/	✅ Active	feedback-prompt.md

Outreach Workers

Worker Name	Location	Status	Feedback Prompt
Event Follow-Up	workers/outreach/event-follow-up/	✅ Active	feedback-prompt.md
LinkedIn Sequence	workers/outreach/linkedin-sequence/	✅ Active	feedback-prompt.md
Ticket Event Follow-Up	workers/outreach/ticket-event-follow-up/	✅ Active	feedback-prompt.md
VP Partnerships	workers/outreach/vp-partnerships/	✅ Active	feedback-prompt.md
Partner Intro Email	workers/outreach/partner-intro-email/	🧪 Planned	feedback-prompt.md

Analysis Workers

Worker Name	Location	Status	Feedback Prompt
ICP Analysis	workers/analysis/icp-analysis/	✅ Active	feedback-prompt.md
Metrics Teardown	workers/analysis/metrics-teardown/	✅ Active	feedback-prompt.md
Partner 90-Day Review	workers/analysis/partner-90d-review/	🧪 Planned	feedback-prompt.md

Operations Workers

Worker Name	Location	Status	Feedback Prompt
Ticket Creation	workers/operations/ticket-creation/	✅ Active	feedback-prompt.md
Meeting Prep	.cursor/skills/meeting-prep/SKILL.md	✅ Active	— (Cursor skill; reads vault client + unassigned transcripts, client Linear board when available)

---

Multi-Worker Workflows

Workflow Name	Location	Workers Used
Campaign Launch	workflows/campaign-launch-workflow.md	Brief Intake → Design-Ready Copy → Campaign Post → Message Sequence → Slack Deployment
Event to Meeting	workflows/event-to-meeting-workflow.md	ICP Analysis → Event Follow-Up → Message Sequence
Deployment	workflows/deployment-workflow.md	[Any Worker] → Slack Deployment → Feedback Loop
90-Day Partner Activation	workflows/partner-activation-90d-workflow.md	VP Partnerships → Partner Intro Email → Partner Co‑Sell Assets (+ content workers) → Partner 90-Day Review

---

Worker Structure

Each worker lives in workers/[category]/[worker-name]/:

workers/[category]/[worker-name]/
├── PRD.md                    # Product requirements (what it does, inputs, outputs)
├── feedback-prompt.md         # Feedback template
└── examples/                 # Example runs/outputs (optional)

---

How to Add a New Worker

1. Create worker directory: workers/[category]/[worker-name]/
2. Create PRD.md: Define what the worker does, inputs, outputs, rules
3. Create feedback-prompt.md: Copy from similar worker and customize
4. Add to this registry: Update table above
5. First run: Prompt for feedback → log run → analyze patterns

---

Related

• Architecture - Structure design
• Feedback Loop - How feedback works
• Run Log - All worker runs logged here
• Patterns - Learned patterns from runs
• Context Graph - Process knowledge