Coordinates agent-to-lead communication via five structured message types.
npx skills add https://github.com/ZeiZel/dotfiles --skill team-comms
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
This protocol enables reliable bidirectional communication between agents and a team lead, providing structured messaging to coordinate work, escalate blockers, and share progress.
Implement the five message types and team context flow to enable coordinated multi-agent teamwork.
High-intent search queries and answers about installing and using this skill.
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.
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.
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.
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.
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.
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.
adamrdrewDefine and enforce agent role responsibilities and boundaries for software projects.
tdp1999Align progress.md with task files and archive completed tasks.
silver2dreamCoordinates AWK automation workflow phases from kickoff to PR review via contract-driven routing and dispatch synchronization.
ArogyaReddyFormalize agent team messaging protocols with plan approvals and shutdown procedures.
