agent-protocol

Orchestrates multi-agent waves to triage, delegate, and serially integrate backlog work.

Updated Jun 28, 2026
One-click install
npx skills add https://github.com/sicambria/talkteach-asr --skill agent-protocol-sicambria
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: agent-protocol
Source: https://github.com/sicambria/talkteach-asr/tree/main/.claude/skills/agent-protocol
Command: npx skills add https://github.com/sicambria/talkteach-asr --skill agent-protocol-sicambria

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Draining a large backlog with parallel AI agents silently degrades without discipline: agents self-merge into race conditions, ship confident no-ops, and drop work on timeouts. This Skill provides a repeatable nine-phase protocol that keeps a fleet of delegated agents honest from triage through integration. ## Core Features & Use Cases - Nine-phase orchestration: Triage, ground, advisor review, clustering, wave spawning, serialized integration, run-to-exhaustion, retro-of-retros, and documented closeout. - Worktree isolation with claims ledger: Each agent works in its own git worktree branched from a pinned base commit, with ownership recorded in a claims file to prevent domain collisions. - Adversarial verification and review quorum: The orchestrator re-runs each branch's gates, scales reviewer count to blast radius, and never lets agents self-merge or self-approve. - Use Case: You have twenty open plans and audit findings in a repo. Invoke the protocol to cluster independent items, spawn a wave of agents that each plan and implement in a worktree, then merge their branches one at a time with verification between each merge. ## Quick Start Ask the AI to drain the backlog with agents using the agent protocol, triaging open plans and running one wave of worktree-based agents with serialized integration.

Frequently Asked Questions about agent-protocol

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

FAQPage Schema
How do I orchestrate multiple AI agents on a backlog?▼

Use a phased protocol: triage every open item, cluster independent work into disjoint domains, spawn one wave of agents in separate git worktrees, then merge branches serially through an orchestrator that verifies each one. Repeat waves until the backlog is drained.

How do I prevent parallel AI agents from conflicting on git merges?▼

Assign each agent its own git worktree branched from a pinned base commit, record ownership in a claims file, and never let agents self-merge. The orchestrator integrates branches one at a time with a verification pass between merges.

When should I not use multi-agent orchestration?▼

Skip it for one- or two-file changes you can finish inline, or when every remaining item is gated or serial. It also requires explicit opt-in since it spends significant tokens across many parallel request streams.

Why do AI agents ship confident no-ops and how do I catch them?▼

Agents may return success summaries without real changes, such as suppressions under wrong config keys. Catch this by adversarially re-running each branch's own verification gate yourself and confirming the mechanism actually takes effect, not just that files changed.

What should I do when an agent times out or disconnects mid-task?▼

A timeout does not mean failure. Inspect the agent's worktree git state directly: the work may be finished and committed, or finished but uncommitted. Commit it yourself if the work is done and correct.