Status: 📋 Ready to Start Approach: 4 parallel Claude Code bot sessions Timeline: 12 weeks to production MVP Architecture: LangGraph-based multi-agent orchestration system
This is a production-ready multi-agent system where specialized AI agents collaborate to build software. The unique aspect: this project itself is being built by 4 Claude Code bots working in parallel, demonstrating the very collaboration patterns the system enables.
- Analyzes user requests and breaks them into agent tasks (Chooser Bot)
- Orchestrates specialized agents to complete complex software projects (LangGraph)
- Tracks real-time progress with human-friendly status (Foreman Bot)
- Optimizes costs by selecting appropriate models (80-95% savings)
- Enables human oversight at critical decision points
Meta-orchestration: A cheap model ($0.0001/call) analyzes tasks and coordinates expensive models, achieving massive cost savings while maintaining quality.
-
ONBOARDING_PROMPTS.md ⭐ START HERE
- Copy-paste prompts to start each of 4 Claude Code bots
- Quick start checklist
- Troubleshooting guide
-
- How the 4 bots work together
- Interface contracts
- Git workflow
- Integration checkpoints
-
- Core framework & orchestration
- LangGraph workflow
- Chooser Bot & Foreman Bot
- State management
-
- Specialized agent implementation
- Model clients (OpenAI, Anthropic, Groq)
- Intelligent model selection
- Agent registry
-
- PostgreSQL & Redis setup
- Docker Compose
- OpenTelemetry observability
- CI/CD pipeline
-
- FastAPI REST API
- Beautiful CLI (Click + Rich)
- React web dashboard
- Real-time monitoring
- MASTER_PROJECT_REFERENCE.md
- Complete system architecture
- Technology stack
- Database schemas
- Interface contracts
- Shared by all bots
-
- Analysis of 4 existing multi-agent approaches
- What worked, what didn't
- Key learnings
-
- Industry research (AutoGen, CrewAI, LangGraph)
- Orchestration patterns
- Best practices
- Cost optimization strategies
-
COMPREHENSIVE_MULTI_AGENT_PLAN.md
- Complete implementation plan
- Full architecture diagrams
- 12-week roadmap
- Cost analysis
# Read these in order:
1. This README (you are here!)
2. ONBOARDING_PROMPTS.md
3. BOT_COORDINATION_GUIDE.md
4. Skim MASTER_PROJECT_REFERENCE.md# Initialize git repo
cd multiagent-project
git init
git add .
git commit -m "Initial commit: 4-bot parallel development setup"
# Create branches
git checkout -b develop
git push origin develop
# Create bot branches
git checkout -b bot1-framework
git checkout -b bot2-agents
git checkout -b bot3-infrastructure
git checkout -b bot4-interfaces
# Push all branches
git push origin --all- Open 4 terminal/VSCode windows
- In each, start Claude Code
- Copy the appropriate prompt from ONBOARDING_PROMPTS.md
- Bot 1: Framework & Orchestration prompt
- Bot 2: Agent Implementation prompt
- Bot 3: Infrastructure & Observability prompt
- Bot 4: User Interfaces & API prompt
- Paste prompt into each Claude Code session
Daily (5 min):
- Check each bot's progress
- Ensure each bot commits daily
- Look for blockers
Weekly (Friday, 2 hours):
- All bots merge to
develop - Run integration tests
- Fix any conflicts
- Plan next week
Week 1 Test:
docker-compose up -d
pytest tests/integration/test_basic.pyWeek 2 Test:
multiagent create "Generate hello world function"
multiagent status <task-id>Week 3 Test:
# Full E2E
pytest tests/e2e/Branch: bot1-framework
Focus: Core engine
Key Files:
multiagent/core/agent.py- BaseAgent interfacemultiagent/core/state.py- State managementmultiagent/core/graph.py- LangGraph workflowmultiagent/core/chooser.py- Chooser Botmultiagent/core/foreman.py- Foreman Bot
Dependencies: Bot 3 (database) - can mock
Provides: BaseAgent interface → Bot 2, Workflow → Bot 4
Branch: bot2-agents
Focus: AI workers
Key Files:
multiagent/models/openai_client.py- OpenAImultiagent/models/anthropic_client.py- Claudemultiagent/models/groq_client.py- Groqmultiagent/models/selector.py- Model selectionmultiagent/agents/development/code_generator.pymultiagent/agents/quality/code_reviewer.py
Dependencies: Bot 1 (BaseAgent) - can mock
Provides: 10+ specialized agents
Branch: bot3-infrastructure
Focus: Foundation
Key Files:
docker/docker-compose.yml- Servicesdocker/init.sql- Database schemamultiagent/infrastructure/database.py- PostgreSQL clientmultiagent/infrastructure/redis_client.py- Redis clientmultiagent/infrastructure/observability/- Tracing & metrics
Dependencies: None (starts first!)
Provides: Database & Redis → All bots
Branch: bot4-interfaces
Focus: Human interaction
Key Files:
multiagent/api/app.py- FastAPI applicationmultiagent/api/routes/tasks.py- Task endpointsmultiagent/cli/commands.py- CLIweb/src/components/TaskMonitor.tsx- React UI
Dependencies: Bot 1 (workflow), Bot 3 (database) - can mock both
Provides: User-friendly interfaces
graph LR
A[Morning: Check Progress] --> B[Bots Work in Parallel]
B --> C[Bots Commit to Branches]
C --> D[Evening: Review Status]
Each Bot:
- Pull latest from develop
- Work on their tasks
- Commit progress
- Push to their branch
Human Coordinator (You):
- Morning: 5-min check-in with all bots
- Unblock any stuck bots
- Facilitate communication between bots
- Evening: Review day's progress
graph LR
A[Mon-Thu: Independent Work] --> B[Fri AM: Prepare for Merge]
B --> C[Fri PM: Merge to Develop]
C --> D[Sat: Integration Testing]
D --> E[Sun: Fix Issues]
E --> F[Mon: Start Next Week]
Friday Integration:
- Each bot creates PR to develop
- Review code
- Merge all PRs
- Run integration tests
- Fix conflicts
- System test
- All 4 bots set up and working
- Docker Compose running
- BaseAgent interface defined
- Basic API endpoints
- First integration test passes
- LangGraph workflow executes
- 5+ agents implemented
- Chooser Bot working
- Foreman Bot tracking progress
- Can create and complete simple task
- React UI showing real-time updates
- Beautiful CLI with Rich
- Full observability
- All tests passing
- Ready for demo
- ✓ End-to-end task execution works
- ✓ 99%+ test pass rate
- ✓ < 2s API response time (p95)
- ✓ 80-95% cost savings vs. naive approach
- ✓ All 4 bots can merge without conflicts
- ✓ All 4 bots productive simultaneously
- ✓ No bot blocked > 1 day
- ✓ Weekly integrations smooth
- ✓ Code quality high
- ✓ Documentation complete
- ✓ Working multi-agent system
- ✓ Can execute real software development tasks
- ✓ User-friendly interfaces
- ✓ Production-ready quality
- ✓ Demonstrates bot collaboration
- Python 3.11+
- LangGraph 0.2+ (agent orchestration)
- FastAPI 0.104+ (REST API)
- PostgreSQL 15+ (database)
- Redis 7+ (cache/queue)
- React 18+ with TypeScript
- Tailwind CSS 3+ (styling)
- Zustand 4+ (state management)
- OpenAI: GPT-4o, GPT-4o-mini
- Anthropic: Claude Sonnet, Claude Opus
- Groq: Llama 8B, Llama 70B (cost optimization)
- Docker + Docker Compose
- GitHub Actions (CI/CD)
- OpenTelemetry (tracing)
- Prometheus + Grafana (metrics)
- COMPREHENSIVE_MULTI_AGENT_PLAN.md - Full architecture
- MULTI_AGENT_RESEARCH_LOG.md - Why we made these choices
- MASTER_PROJECT_REFERENCE.md - Technical reference
- BOT_COORDINATION_GUIDE.md - How bots work together
- ONBOARDING_PROMPTS.md - Starting each bot
- BOT_X_*_TASKS.md - Detailed task breakdowns
- Each task file has implementation examples
- Acceptance criteria for each task
Solution: Tell bot to create a mock and continue
"Create a mock of [dependency] for now. Document the interface
you expect. Continue with your tasks using the mock."
Solution: Coordinate bot discussion
"Bot X and Bot Y, you have a conflict in [file].
Bot X changed: [describe]
Bot Y changed: [describe]
Discuss and resolve - refer to MASTER_PROJECT_REFERENCE.md."
Solution: Systematic debugging
1. Which component failing?
2. Check that bot's unit tests
3. Review interface contract
4. Fix and re-test
Solution: Simplify and parallelize
"Bots: Focus on making it work first, optimize later.
Use TODO comments for improvements.
What can you do right now with mocks?"
Read First:
- Your bot's task file
- MASTER_PROJECT_REFERENCE.md
- BOT_COORDINATION_GUIDE.md
Still Stuck?:
- Check if you can use a mock
- Review interface contracts
- Look at similar code in research docs
Refer To:
- COMPREHENSIVE_MULTI_AGENT_PLAN.md - Overall design
- MULTI_AGENT_RESEARCH_LOG.md - Best practices
- MULTI_AGENT_APPROACHES_LOG.md - What others did
Before starting the 4-bot team:
- Read this README completely
- Read ONBOARDING_PROMPTS.md
- Skim BOT_COORDINATION_GUIDE.md
- Git repository initialized
- All 4 branches created
- Have 4 Claude Code sessions ready
- Understand daily/weekly workflow
- Ready to coordinate 4 bots
- Have 12 weeks available
You now have everything you need to build a production-ready multi-agent system with 4 Claude Code bots working in parallel.
- ✅ Read ONBOARDING_PROMPTS.md
- ✅ Start 4 Claude Code sessions
- ✅ Let them work!
- ✅ Check progress daily
- ✅ Integrate weekly
- ✅ Ship in 12 weeks
multiagent-project/
├── README.md ⭐ You are here
├── ONBOARDING_PROMPTS.md ⭐ Start here next
├── BOT_COORDINATION_GUIDE.md
├── MASTER_PROJECT_REFERENCE.md
├── BOT_1_FRAMEWORK_TASKS.md
├── BOT_2_AGENTS_TASKS.md
├── BOT_3_INFRASTRUCTURE_TASKS.md
├── BOT_4_INTERFACES_TASKS.md
│
└── multiagent/ (Created by bots)
├── core/ (Bot 1)
├── agents/ (Bot 2)
├── models/ (Bot 2)
├── infrastructure/ (Bot 3)
├── api/ (Bot 4)
├── cli/ (Bot 4)
├── web/ (Bot 4)
└── tests/ (All bots)
Built with: Claude Code (×4) Approach: Parallel bot development Innovation: Meta-orchestration with 80-95% cost savings Timeline: 12 weeks to production MVP Status: 📋 Ready to start!
Let's build the future of multi-agent systems - with multiple agents! 🚀