Team Communication Protocols

Team Communication Protocols

What Is This

The "Team Communication Protocols" skill provides structured messaging standards for communication within autonomous agent teams. It defines how agents should select appropriate message types, manage plan approvals, handle coordinated shutdowns, and avoid common anti-patterns in distributed teamwork. By explicitly specifying communication norms, this skill ensures that agent teams can operate efficiently, minimize misunderstandings, and maintain reliable task coordination at every stage of a project.

Why Use It

Effective team communication is essential in both human and agent-based collaboration. In agent teams, ambiguity regarding message intent or recipient can lead to task duplication, missed integration points, or incomplete shutdowns. This skill provides clear guidelines for:

• Choosing the correct message type for each scenario
• Ensuring plans are reviewed and approved before execution
• Coordinating orderly shutdowns once work concludes
• Discovering and referencing team member roles and capabilities

By using this skill, agent teams reduce communication errors, support traceable workflows, and streamline task handoffs. It is especially critical in multi-agent systems where clear boundaries and expectations prevent coordination breakdowns.

How to Use It

Message Type Selection

Selecting the correct message type is foundational to effective agent communication. The protocol defines three primary message types: message, broadcast, and shutdown_request.

1. message (Direct Message)

A direct message targets a specific teammate and is the default communication form for most one-to-one interactions.

Example:

{
  "type": "message",
  "recipient": "implementer-1",
  "content": "Your API endpoint is ready. You can now build the frontend form.",
  "summary": "API endpoint ready for frontend"
}

Use for:

• Task updates
• Coordination between roles
• Direct questions
• Integration notifications

2. broadcast (To All Teammates)

A broadcast sends the same message to all team members simultaneously. Use broadcasts when information is relevant to the whole team, such as announcing a completed milestone or sharing critical context.

Example:

{
  "type": "broadcast",
  "content": "The deployment will begin in 10 minutes. Please ensure all work is saved.",
  "summary": "Deployment notice"
}

Use for:

• Announcements
• Global warnings
• Shared status updates

3. shutdown_request (Initiate Team Shutdown)

A shutdown request is a specialized message used to trigger a coordinated team shutdown. This ensures all agents complete their tasks and gracefully terminate operations.

Example:

{
  "type": "shutdown_request",
  "content": "All assigned tasks are complete. Please confirm shutdown readiness.",
  "summary": "Requesting team shutdown"
}

Use for:

• Ending the team's lifecycle
• Signaling project completion
• Coordinated resource release

Plan Approval Workflows

For critical tasks or those requiring oversight, the protocol supports plan approval workflows. An implementer submits a proposed plan as a direct message to the team lead, who reviews, approves, or requests changes.

Example:

Implementer sends:

{
  "type": "message",
  "recipient": "team-lead",
  "content": "Attached is my API implementation plan for review.",
  "summary": "Requesting plan approval"
}

Team lead replies:

{
  "type": "message",
  "recipient": "implementer-1",
  "content": "Plan approved. Proceed with implementation.",
  "summary": "Plan approved"
}

Graceful Team Shutdown

When all tasks are complete, use the shutdown_request message to coordinate a clean shutdown. Each agent should confirm readiness before the team lead issues the final shutdown command. This prevents resource leaks and ensures no work is left uncompleted.

Discovering Teammate Identities and Capabilities

Agents may need to query or broadcast their roles and capabilities. Use direct messages to request information or broadcasts to share capabilities with the full team, enabling dynamic role assignment and effective delegation.

When to Use It

Apply the "Team Communication Protocols" skill in scenarios such as:

• Forming a new agent team and establishing initial communication norms
• Setting up workflows where plan approval is mandatory before task execution
• Deciding whether to direct a message to a single agent or broadcast to all
• Orchestrating an orderly team shutdown after project completion
• Debugging coordination failures or integration issues among agents

Important Notes

• Default to Direct Messages: Use direct messages for most interactions unless the information is universally relevant.
• Limit Broadcasts: Overuse of broadcasts can cause information overload and reduce clarity. Use them judiciously for team-wide announcements only.
• Enforce Plan Approval: Always require explicit approval for critical or risky operations to reduce errors and ensure accountability.
• Graceful Shutdowns: Never terminate a team abruptly. Always coordinate shutdowns with confirmation from all agents.
• Avoid Anti-Patterns: Do not send ambiguous messages lacking clear recipients or context. Avoid sending sensitive or private information via broadcast.
• Traceability: Include clear and concise summaries in every message to facilitate monitoring and debugging.

By following these structured protocols, agent teams can maximize productivity, minimize miscommunications, and ensure robust, reliable collaborative workflows.