Agent Protocols

Shared behavioral protocols for all agents in the workflow-team pipeline.

1. Recursive Nesting Protocol

When your scope card is too broad for a single context:

1. Further decompose using parallel-dispatch skill (§1 Decomposition, §5 Hierarchical Decomposition)
2. Spawn sub-agents with narrower scope cards using TypeName="self" with dedicated Role designations (see §3 Agent Spawn Protocol)
3. Your scope becomes the ceiling — children cannot operate outside it
4. Track sub-agent progress; merge results when all complete
5. Write .agentwork/handoff.md for your parent coordinator

Triggers for nesting:

• Task edits >3 unrelated files
• Scope card contains >2 features
• Context approaching 50% capacity
• Secondary expertise needed (delegate to specialist)

2. Pre-Implementation Restatement

Before writing code, restate in your own words:

1. What the .agentwork/brief.md / scope card asks you to build
2. What files you will create or modify
3. What assumptions you are making

If any assumption is uncertain, document it in your handoff and proceed with the conservative interpretation.

3. Agent Spawn Protocol (Universal TypeName="self" Pattern)

In the Antigravity subagent platform, TypeName="self" is the universal spawn mechanism that ensures subagents inherit their parent's full tool capabilities (file modification, command execution, and subagent dispatch for multi-tier nesting). Discovered named types default to read-only tool sets.

When spawning ANY agent type with a role file in .agents/agents/:

1. Always use TypeName="self" in invoke_subagent calls. This guarantees the subagent inherits write, execution, and subagent tools from the parent.
2. Differentiate roles via the Role field (e.g., Role: "Tech-Lead (Auth API)", Role: "Backend Engineer (Payments)", Role: "Test Automation Engineer").
3. Reference the role file in the system prompt — never paraphrase:

   "Your role, domain, skills, boundaries, and protocols are defined in
    file://{workspace}/.agents/agents/{agent-type}.md.
   Read this file FIRST before beginning any work."
   

4. The child agent MUST read the role file as its first action. Boundaries, domain rules, and workflow expectations are strictly defined by the role file.
5. Propagate this protocol recursively — Tech-Leads spawn specialized builders using TypeName="self" with builder role files, enabling deep parallel execution.
6. Subagent Monitoring & Reactivity: Parents receive automatic notifications when subagents send messages. Wait reactively or use manage_subagents to list active subagents. Do NOT use manage_task (which is exclusively for background commands/processes) for subagent lifecycle operations.

4. Parallel Dispatch Format

Each agent file contains a ## Parallel Dispatch section with role-specific values. The standard fields are:

Field	Purpose
Scope Axis	The dimension used to partition work (feature, concern, domain)
Write Scope	Glob pattern for exclusive write access
Shared Reads	Glob patterns for read-only access
Constraint	Key limitation on parallel instances
Integration	How parallel results are reconciled (if applicable)

For read-only agents, Write Scope becomes Read Scope and scoping is for coverage guarantee, not conflict prevention.

5. Completion Reporting Protocol

Every agent MUST report completion to its parent. This is non-negotiable.

For code-writing agents (builders, specialists):

1. Write .agentwork/handoff.md with status and file manifest
2. Message your parent (the conversation that dispatched you): ".agentwork/handoff.md ready — [scope-card-id] [COMPLETE|BLOCKED]"

For read-only agents (scouts, reviewers, red team members):

1. Write your deliverable file (findings, verdict, etc.)
2. Message your parent: ".agentwork/[deliverable-file] ready — [1-line summary]"

Critical: Reply-To Address

Your parent's conversation ID is the conversation that sent you your initial task. This is the conversation you received your first message from. Always reply to THIS conversation ID — never to any other ID mentioned in your task description or context.

6. Sovereign Subagent Awareness

Coordinators and tech-leads MUST proactively delegate to specialized builders when the work warrants it. This protocol ensures maximum parallelism, speed, and quality across the pipeline.

[!IMPORTANT] Scope: This mandate applies to agents that receive and decompose scope cards — conductors, tech-leads, and any agent with a ## Scope Card Execution section. It does NOT apply to pipeline supervisors (overseer) whose role is limited to spawning coordinators and monitoring pipeline flow. The overseer spawns ONLY @conductor and @red-team-lead — it NEVER directly spawns tech-leads, builders, reviewers, scouts, or design specialists.

When to spawn sovereign subagents:

• Your scope card spans multiple domains (e.g., backend + frontend + tests)
• Your task contains independently parallelizable sub-deliverables
• A sub-task requires secondary expertise (e.g., you are a tech-lead but the work is pure frontend — delegate to @frontend-engineer)
• The parallel-dispatch skill's nesting triggers fire (>3 files, >2 features, >50% context)

When NOT to spawn (do the work yourself):

• The task is trivially small (<3 files, single concern, <50 lines of integration code)
• You ARE the specialist for this domain (e.g., you are @backend-engineer and it's a backend task)
• Spawning would create more overhead than value (single-file fix, quick config change)
• You are a pipeline supervisor (overseer) — delegate to your conductor, not to builders

Sovereignty principle:

Each spawned subagent operates autonomously within its scope card boundaries. It reads its role file, loads its skills, makes implementation decisions, runs its own quality checks, and reports completion. The parent does NOT micromanage — it decomposes, dispatches, and validates results.

Anti-pattern: A Tech-Lead implementing all backend + frontend + test code itself instead of dispatching @backend-engineer, @frontend-engineer, and @test-automation-engineer in parallel. This defeats the purpose of the multi-agent hierarchy and serializes work that could run concurrently.

Anti-pattern: An Overseer spawning tech-leads, builders, or design specialists directly instead of spawning a Conductor and letting the Conductor manage the build hierarchy. This flattens the pipeline and removes orchestration control.