team-comms

Coordinates agent-to-lead communication via five structured message types.

2|Updated Oct 1, 2024

Search Tags:#workflow #protocol #agents #escalation #team-communication #sendmessage

Ready to run

npx skills add https://github.com/ZeiZel/dotfiles --skill team-comms

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: team-comms
Source: https://github.com/ZeiZel/dotfiles/tree/main/.claude/skills/team-comms
Command: npx skills add https://github.com/ZeiZel/dotfiles --skill team-comms

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This protocol enables reliable bidirectional communication between agents and a team lead, providing structured messaging to coordinate work, escalate blockers, and share progress.

Core Features & Use Cases

Message types: PROGRESS, QUESTION, BLOCKER, DONE, SUGGESTION to standardize interactions.
Team Context Block injection for consistent context and routing.
Escalation rules and clear ownership to prevent silos and miscommunication.
Use Case: coordinating a complex feature across multiple agents and roles.

Quick Start

Implement the five message types and team context flow to enable coordinated multi-agent teamwork.

Frequently Asked Questions about team-comms

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I coordinate bidirectional team communication across multiple agents?▼

You can coordinate bidirectional team communication by implementing structured message types like PROGRESS, QUESTION, BLOCKER, DONE, and SUGGESTION. This standardizes interactions between agents and the team lead to ensure aligned progress and clear handoffs.

What is the best way to escalate blockers in a multi-agent workflow?▼

Escalating blockers in a multi-agent workflow requires applying specific escalation rules and clear ownership protocols. Using a structured BLOCKER message type within a Team Context block ensures rapid resolution and prevents communication silos.

How does a Team Context block work for agent communication protocols?▼

A Team Context block works by injecting consistent context and routing information into agent messages. This ensures that every agent in the workflow receives identifiable roles and structured messaging for systematic coordination.

Do I need specific dependencies to use structured messaging for multi-agent coordination?▼

No specific dependencies are required to use structured messaging for multi-agent coordination. You can implement the five message types and team context flow directly within your existing agents to enable coordinated teamwork.

Can I use this protocol to standardize interactions for complex feature development across roles?▼

Yes, you can use this protocol to standardize interactions for complex feature development across multiple agents and roles. It provides structured messaging and escalation rules to coordinate work and share progress effectively.

When should I not use a bidirectional team communication protocol for agents?▼

You should not use a bidirectional team communication protocol for simple, single-agent tasks that do not require coordinated work. The protocol is designed for complex multi-agent workflows needing structured messaging, escalation rules, and traceability.