team-communication-protocols

To prevent work from stalling at handoff points, you structure agent team communication using direct messages, broadcasts, and shutdown requests based on urgency and audience. This approach enforces consistent recipient naming and messaging hygiene to avoid collaboration failures.

The best way to manage plan approval is to use a structured workflow that reviews, approves, or rejects a teammate's plan before implementation begins. This ensures agent coordination remains structured and prevents unreviewed work from proceeding.

Use broadcasts for critical shared updates like contract changes and direct messages for targeted updates like notifying one implementer that an API is ready. Selective broadcast use prevents noisy messaging and maintains coordination hygiene across agent teams.

To handle shutdown requests for agents after task completion, you use graceful shutdown handling protocols. This cleanly terminates teammates after work is complete, preventing stale interfaces and avoiding messaging anti-patterns during the teardown process.

Common messaging anti-patterns to avoid in agent coordination include noisy broadcasts, stale interfaces, and identity confusion. Avoiding these collaboration anti-patterns requires consistent recipient naming and selective message selection to keep teams unblocked.