agent-collab-protocol

star 0

Use when an agent must coordinate with other AI agents through files in tmp/agent-collab, hand off work between planner, implementer, reviewer, coordinator, or human roles, or follow a document-based multi-agent workflow without network/API communication.

Gn0lee By Gn0lee schedule Updated 6/11/2026

name: agent-collab-protocol description: "Use when an agent must coordinate with other AI agents through files in tmp/agent-collab, hand off work between planner, implementer, reviewer, coordinator, or human roles, or follow a document-based multi-agent workflow without network/API communication."

Agent Collab Protocol

Use this as the shared contract for file-based collaboration between any agents. Agents may be Codex, Claude Code, Antigravity, or another tool; the protocol uses roles, not product names.

Directory

Use this directory in the current worktree:

tmp/agent-collab/

The worktree is the task boundary. Do not create issue-specific subdirectories unless the user explicitly asks for that.

Files

tmp/agent-collab/
├── handoff.yml
├── plan.md
├── questions.md
├── implementation-report.md
├── review.md
└── decisions.md
  • handoff.yml: single source of truth for current status, owner role, required reads, and required writes.
  • plan.md: decision-complete implementation plan written by planner.
  • questions.md: blocked questions that require planner, reviewer, coordinator, or human input.
  • implementation-report.md: implementation summary and verification written by implementer.
  • review.md: approval or requested changes written by reviewer.
  • decisions.md: durable decisions that should prevent repeated debate.

These coordination files are working artifacts. Do not include tmp/agent-collab/ in implementation commits unless the user explicitly asks for it.

Handoff Schema

Use this shape for handoff.yml:

task:
  title: ""
  issue: null
  branch: ""
status: planning | ready_for_implementation | implementing | ready_for_review | changes_requested | approved | blocked
owner_role: planner | implementer | reviewer | coordinator | human
last_updated_by:
  agent: ""
  role: planner | implementer | reviewer | coordinator | human
last_updated_at: "YYYY-MM-DDTHH:mm:ssZ"
current_request: ""
required_reads: []
required_writes: []
artifacts:
  implementation_commits: []
constraints:
  implementation_mode: sequential
  implementer_may_change_plan: false
  coordination_files_committed: false

State Flow

Normal flow:

planning -> ready_for_implementation -> implementing -> ready_for_review -> approved

Review loop:

ready_for_review -> changes_requested -> implementing -> ready_for_review

Blocked flow:

any status -> blocked

Collaboration Rules

  • Read handoff.yml first.
  • Act only when owner_role matches your role, unless the user explicitly asks you to inspect or recover the workflow.
  • Read every path in required_reads before doing role work.
  • Write only files owned by your role.
  • Do not overwrite another role's document except to append clearly marked responses when that file's format allows it.
  • Keep implementation sequential by default: one implementer works at a time.
  • Treat implementer_may_change_plan: false as a hard stop. Implementers may not redesign; they must ask.
  • If required inputs are missing, create or update questions.md, set status: blocked, and set owner_role to the role that can answer.
  • Before ending any role turn, reread handoff.yml and verify that status, owner_role, current_request, required_reads, and required_writes match the actual next action.
  • Treat a missing required write as incomplete work. Update the role-owned document and handoff.yml before handing off.

Status Updates

When handing off, update handoff.yml with:

  • the next status
  • the next owner_role
  • last_updated_by.agent
  • last_updated_by.role
  • last_updated_at
  • a concrete current_request
  • exact required_reads and required_writes
  • artifacts.implementation_commits when implementation commits exist

Commit Policy

  • Planner, reviewer, coordinator, and protocol-only updates do not create commits.
  • Implementer commits product code changes before each ready_for_review handoff.
  • When addressing requested changes, implementer creates a new follow-up commit instead of amending the previous implementation commit, unless the user explicitly asks otherwise.
  • Commit only implementation artifacts that belong in the repository. Keep tmp/agent-collab/ uncommitted by default.
  • Record commit hashes in implementation-report.md and handoff.yml.

Handoff Completion Checklist

Before handing off, confirm:

  • Every path in required_reads was read.
  • Every path in required_writes was created or updated.
  • The next owner_role matches the next status.
  • current_request is an executable instruction for the next role.
  • tmp/agent-collab/ coordination files are not staged for commit unless explicitly requested.
Install via CLI
npx skills add https://github.com/Gn0lee/oat --skill agent-collab-protocol
Repository Details
star Stars 0
call_split Forks 0
navigation Branch main
article Path SKILL.md
More from Creator