team-protocol

Coordinate multi-agent team communication with append-only event logging and role-based routing.

4|Updated Jun 1, 2026
One-click install
npx skills add https://github.com/vmobifystudio/app-dev-team --skill team-protocol
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: team-protocol
Source: https://github.com/vmobifystudio/app-dev-team/tree/main/skills/team-protocol
Command: npx skills add https://github.com/vmobifystudio/app-dev-team --skill team-protocol

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents multi-agent software teams from losing decisions, duplicating questions, creating communication loops, or shipping work based on unresolved assumptions.

Core Features & Use Cases

  • Durable Team Ledger: Records questions, answers, handoffs, blockers, decisions, escalations, and project updates in an append-only event log.
  • Governed Collaboration: Enforces communication routes, anti-ping-pong limits, message obligations, escalation rules, and artifact registration.
  • Workflow Accountability: Coordinates mid-sprint question resolution, standardized ticket output contracts, evidence bundles, branch requirements, and release-oriented verification.
  • Use Case: When an Android developer encounters an unresolved implementation choice, use this Skill to route the question to the appropriate role, preserve the decision in the team ledger, and ensure it is delivered into a specification, artifact, or ticket transition.

Quick Start

Use the team protocol skill to record and route a blocking implementation question on a specific ticket while enforcing the team’s communication and escalation rules.

Frequently Asked Questions about team-protocol

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

FAQPage Schema
How do I track decisions and unresolved questions across a multi-agent software development team?

Multi-agent team coordination tracks decisions and unresolved questions using an append-only event ledger. It routes blockers, specification queries, and handoffs to appropriate roles while preserving answers in a durable log for ticket transitions.

What is the best way to prevent communication loops and duplicated questions during mid-sprint development?

Preventing communication loops requires governed collaboration rules with anti-ping-pong limits and message obligations. The team protocol enforces standardized output contracts, evidence requirements, and role-based routing to eliminate duplicated questions.

How do I manage escalations and ticket workflows when AI agents encounter unresolved implementation choices?

Managing escalations and ticket workflows uses role-based routing with user escalation safeguards. When agents hit unresolved implementation choices, the protocol records the blocker and routes it to the correct role for resolution before artifact delivery.

Can I use an append-only event ledger for cross-platform divergence coordination and branch requirements?

An append-only event ledger coordinates cross-platform divergences by enforcing branch requirements and release-oriented verification. It logs mid-sprint Q&A, handoffs, and specification questions to ensure teams ship work based on resolved decisions.

When do I need standardized output contracts and evidence bundles for team handoffs?

Standardized output contracts and evidence bundles are needed when coordinating multi-agent handoffs across ticket workflows. They enforce artifact registration and delivery, ensuring developers receive verified evidence before transitioning tickets or branches.