Team Topology — Who Does What
One human, one AI orchestrator, two AI execution agents, BMAD planning agents across 6 modules. GitHub is the sausage maker.
The Machine
The flow:
- Claude routes to BMAD (brainstorm/plan) or Pulp Fiction Crew (engineering workflow)
- GitHub receives the PR — labels route it to the right reviewer
- Max (product) or Hank (engineering) does full review, kicks back questions if needed
- Approve → merge → Vercel → live
- Telegram — Ryan can ping Max or Hank in parallel at any point
Workflow State Machine
| State | Owner | Max Wait | Escalation |
|---|---|---|---|
| Draft | Claude / BMAD agent | — | — |
| PR Created | Claude | 1 hour | Auto-assign if no assignee |
| Assigned | Max or Hank | 4 hours | Telegram ping → Ryan |
| In Review | Max or Hank | 8 hours | Telegram ping → Ryan |
| Changes Requested | Claude / originator | 4 hours | Re-ping assignee |
| Approved | Reviewer | 1 hour | Auto-merge if checks pass |
| Merged | GitHub Actions | Immediate | — |
30-Second Operator Runbook
- Create Issue or PR with one of:
product,engineering,docs,ui-uxlabel - Assign to
@beliefengines/product(Max) or@beliefengines/engineering(Hank) - Expected first response: 4 hours
- If no response: ping on Telegram
- If still no response: Ryan escalates directly
How It Feels
Agent Profiles
Claude — Orchestrator
- Scope: Global across all repos
- Role: Strategy, planning, delegation, quality gate
- Tools: BMAD agents, Pulp Fiction crew, MCP servers
- Policy: Not in product runtime. Strategy/orchestration layer only.
Max Power — Product / Design Lead
- Platform: OpenClaw (iMac mini)
- Reach: GitHub + Telegram
- Role: Product, design, UI/UX, implementation
- Strengths: Fast triage, screenshots/PRs as proof, mobile-first QA
- Best input: Objective + deadline + must-haves + approval workflow
Hank Scorpio — Engineering Lead
- Platform: OpenClaw (localhost)
- Reach: GitHub + Telegram
- Role: Engineering execution, code review, infra, pipeline
- Strengths: Fast prototype-to-deploy, systematic review
- Best input: Concrete outcome + hard constraints + authority boundaries
Communication Channels
| Channel | Purpose |
|---|---|
| Claude Code CLI | BMAD sessions — brainstorm, plan, create |
| GitHub | The sausage maker — PRs, issues, actions, boards |
| Telegram | Ping Max/Hank in parallel, real-time chat, approvals |
| Wiki | Source of truth — published docs, decisions |
PM Stack
GitHub Projects with 4 boards:
- Product — features, roadmap items
- Engineering — technical tasks, infra
- UI-UX — design, visual lock, mobile QA
- DevOps — deploys, observability, pipeline