Brainforge Knowledge

MIGRATION_PLAN

2 min read

Agent Structure Migration Plan

Purpose: Step-by-step plan to reorganize all agents into unified workers/ structure
Status: Ready to execute
Date: 2026-02-05

Current State

Agents are scattered:

  • gtm/agents/ - Some agents (message sequence, design-ready copy)
  • knowledge/sales/campaign-launch/ - Campaign brief intake
  • gtm/agents/.claude/agents/ - Event follow-up, LinkedIn sequence
  • knowledge/sales/partners/agents/ - VP partnerships (legacy path was gtm/partnerships/agents/)
  • Implicit agents (campaign post, slack deployment)

Target State

Unified structure:

gtm/agents/
├── workers/          # All individual agents
├── workflows/        # Multi-agent coordination
├── shared/           # Shared infrastructure
└── examples/         # Example runs

Migration Steps

Step 1: Create New Structure

  • Create ARCHITECTURE.md (structure design)
  • Create workers/ directory structure
  • Create workflows/ directory
  • Create shared/ directory structure
  • Create examples/ directory

Step 2: Move Workers

Content Generation:

  • Move PRD-design-ready-copy-agent.md → workers/content-generation/design-ready-copy/PRD.md
  • Move feedback-prompts/design-ready-copy-agent.md → workers/content-generation/design-ready-copy/feedback-prompt.md
  • Create workers/content-generation/campaign-post/ (new)
  • Create workers/content-generation/slack-deployment/ (new)

Campaign Planning:

  • Move campaign-launch/CAMPAIGN_BRIEF_INTAKE.md → workers/campaign-planning/campaign-brief-intake/PRD.md
  • Move feedback-prompts/campaign-brief-agent.md → workers/campaign-planning/campaign-brief-intake/feedback-prompt.md
  • Move MESSAGE_SEQUENCE_AGENT.md → workers/campaign-planning/message-sequence/PRD.md
  • Move playbooks/ → workers/campaign-planning/message-sequence/playbooks/

Outreach:

  • Move .claude/agents/event-follow-up-agent.md → workers/outreach/event-follow-up/PRD.md
  • Move .claude/agents/linkedin-sequence-agent.md → workers/outreach/linkedin-sequence/PRD.md
  • Move TICKET_EVENT_FOLLOW_UP_AGENT.md → workers/outreach/ticket-event-follow-up/PRD.md
  • Move partners/agents/vp-partnerships-agent.md → workers/outreach/vp-partnerships/PRD.md

Analysis:

  • Move prompts/icp-agent-prompt.md → workers/analysis/icp-analysis/PRD.md
  • Move playbooks/metrics-teardown-agent.md → workers/analysis/metrics-teardown/PRD.md

Operations:

  • Create workers/operations/ticket-creation/ (move ticket creation agent)

Step 3: Move Shared Infrastructure

  • Move AGENT_FEEDBACK_LOOP.md → shared/feedback-loop/AGENT_FEEDBACK_LOOP.md
  • Move FEEDBACK_LOOP_PROCESS.md → shared/feedback-loop/FEEDBACK_LOOP_PROCESS.md
  • Move RUN_LOG.md → shared/feedback-loop/RUN_LOG.md
  • Move CONTEXT_GRAPH_APPROACH.md → shared/context-graph/CONTEXT_GRAPH_APPROACH.md
  • Move PR_CONTEXT_GRAPH_CHECKLIST.md → shared/context-graph/PR_CONTEXT_GRAPH_CHECKLIST.md
  • Move PATTERNS.md → shared/patterns/PATTERNS.md

Step 4: Create Workflows

  • Create workflows/campaign-launch-workflow.md
  • Create workflows/event-to-meeting-workflow.md
  • Create workflows/deployment-workflow.md

Step 5: Update References

  • Update AGENT_REGISTRY.md with new paths
  • Update README.md with new structure
  • Update all feedback prompts with new paths
  • Update any cross-references in docs

Step 6: Archive Old Structure

  • Create archive/ directory
  • Move old files to archive (keep for reference)
  • Add deprecation notices

Execution Order

  1. Create structure (Step 1) - No breaking changes
  2. Move workers (Step 2) - Update paths as we go
  3. Move shared (Step 3) - Update references
  4. Create workflows (Step 4) - New functionality
  5. Update references (Step 5) - Fix broken links
  6. Archive old (Step 6) - Cleanup

Testing Checklist

After migration:

  • All agents accessible via new paths
  • Feedback prompts work
  • Run log still functions
  • Patterns file accessible
  • Workflows documented
  • No broken references

Rollback Plan

If issues arise:

  1. Keep old structure until migration verified
  2. Use symlinks if needed for compatibility
  3. Update references gradually
  4. Archive old structure only after full verification

Graph View

Backlinks