← Back to library

多代理烧 token 时先做职责拆分与 DoD 关卡

针对 5 个代理协作却频繁返工/冲突的实战反馈,沉淀为可执行治理方案:减少并发面、增加验收门槛、再逐步扩容。

REDDITDiscovered 2026-02-12Author u/emilepetrone
Prerequisites
  • Your project already uses Git workflow with PR checks.
  • Each agent role can be reconfigured (prompt/scope/tools).
Steps
  1. Shrink swarm size first (for example 2-3 core roles) and define explicit handoff contracts between roles.
  2. Add DoD gates per role: required artifacts, max PR size, and mandatory tests before handoff.
  3. Introduce token/time budgets per run and stop conditions for repetitive retries.
  4. Use one human approval checkpoint before merge to catch conflict-prone or low-signal changes.
  5. Scale agent count only after two consecutive cycles meet quality and budget targets.
Commands
git status
git log --oneline -n 5
npm run build
openclaw gateway status
Verify

Compared with previous cycle, merge-conflict incidents and retry loops drop while build pass rate improves.

Caveats
  • Discussion post is experiential; exact role templates require environment-specific tuning(需验证).
  • More agents do not guarantee higher throughput when task decomposition is weak.
Source attribution

This tip is aggregated from community/public sources and preserved with attribution.

Open original source ↗
Visit original post