Standalone multi-team orchestration config for OpenCode, extracted from dotbrains/opencode.
Based on IndyDevDan's "One Agent Is NOT ENOUGH".
Orchestrator Lead
├── Planning Team (planning-lead → planning-agent + plan-reviewer)
├── Engineering Team (engineering-lead → frontend-dev + backend-dev + devops-specialist)
└── Validation Team (validation-lead → reviewer + security-reviewer + qa-engineer)
agent/- Orchestrator + team leads/workers + requirements clarifierskills/mt-*- Multi-team workflow skills (mt-feature,mt-review,mt-audit,mt-fix,mt-lookup)expertise/- Team expertise docs (planning,engineering,validation,orchestrator)teams.yaml- Team membership setsorchestrator.yaml- Routing, model tiers, team definitions, preprocessing rulesmulti-team-config.yaml- Compatibility copy oforchestrator.yamlagent-chain.yaml- Sequential chain definitionsMULTI-TEAM.md- Detailed reference docs
cp -R agent ~/.config/opencode/
cp -R skills ~/.config/opencode/
cp -R expertise ~/.config/opencode/
cp teams.yaml orchestrator.yaml agent-chain.yaml ~/.config/opencode/cd ~/.config/opencode
git submodule add <repo-url> multi-teamThen copy/sync the same files from multi-team/ into the root OpenCode config.
- Ensure your OpenCode config (
~/.config/opencode/opencode.json) has:"default_agent": "orchestrator"(optional, but recommended)
- Start OpenCode and use orchestrator directly, or invoke:
@mt-featurefor full lifecycle (plan → engineer → validate)@mt-fixfor bug fix workflow@mt-reviewor@mt-auditfor focused validation/security
| Tier | Model | Use For |
|---|---|---|
| Planning | opencode/nemotron-3-ultra-free |
Orchestrator, planning, architecture |
| Engineering | opencode/north-mini-code-free |
Implementation |
| Validation | opencode/north-mini-code-free |
Review, QA, security |
PolyForm Shield License 1.0.0 (see LICENSE).