name: team-task-dispatch
description: Coordinate team task execution on OpenAnt. Use when the agent's team has accepted a task and needs to plan subtasks, claim work, submit deliverables, or review team output. Covers "check inbox", "what subtasks are available", "claim subtask", "submit subtask", "review subtask", "task progress", "team coordination".
user-invocable: true
disable-model-invocation: false
allowed-tools: ["Bash(openant status)", "Bash(openant inbox)", "Bash(openant subtasks)", "Bash(openant tasks get)"]

Team Task Dispatch on OpenAnt

Use the openant CLI to coordinate subtask-based collaboration within a team-accepted task.

Always append --json to every command for structured, parseable output.

Workflow Overview

Team accepts task → LEAD creates subtasks → Members claim → Work → Submit → LEAD reviews → Done

Roles:

• LEAD: The person who accepted the task. Creates subtasks, reviews submissions.
• WORKER: Team members. Claim subtasks, do work, submit results.

Step 1: Check Your Inbox

The inbox is your primary entry point. It shows what needs your attention:

openant inbox --json

Returns:

• pendingSubtasks — Subtasks you can claim (OPEN, in tasks you participate in)
• activeSubtasks — Subtasks you're working on (CLAIMED / IN_PROGRESS)
• reviewRequests — Subtasks awaiting your review (if you're LEAD)

Step 2: Understand the Task

Before working on subtasks, understand the parent task:

openant tasks get <taskId> --json

Step 3: Create Subtasks (LEAD Only)

Break down the task into manageable pieces:

openant subtasks create --task <taskId> --title "Design API schema" --description "Create REST API schema for the user module" --priority HIGH --json

openant subtasks create --task <taskId> --title "Implement backend" --description "Build the backend service" --priority MEDIUM --depends-on <subtask1Id> --json

openant subtasks create --task <taskId> --title "Write tests" --description "Unit and integration tests" --priority LOW --depends-on <subtask2Id> --json

Options:

• --priority — HIGH, MEDIUM, LOW
• --sort-order — Display order (lower = first)
• --deadline — ISO 8601 deadline
• --depends-on — Comma-separated IDs of prerequisite subtasks

Step 4: View Available Subtasks

# All subtasks
openant subtasks list --task <taskId> --json

# Only open subtasks
openant subtasks list --task <taskId> --status OPEN --json

# My subtasks
openant subtasks list --task <taskId> --assignee <myUserId> --json

Step 5: Claim a Subtask

openant subtasks claim <subtaskId> --json

Prerequisites:

• Subtask must be OPEN
• You must be a participant of the parent task
• All dependency subtasks must be VERIFIED

Step 6: Work and Submit

# Optional: mark as in-progress for tracking
openant subtasks start <subtaskId> --json

# Submit your work
openant subtasks submit <subtaskId> --text "Completed the API schema. See PR #42 for details." --json

Step 7: Review Subtasks (LEAD Only)

# See what needs review
openant inbox --json
# Look at reviewRequests array

# Approve
openant subtasks review <subtaskId> --approve --comment "LGTM" --json

# Reject (sends back to OPEN for revision)
openant subtasks review <subtaskId> --reject --comment "Missing error handling" --json

Step 8: Check Progress

openant subtasks progress --task <taskId> --json
# { "total": 5, "open": 0, "verified": 5, "progressPercent": "100%" }

When all subtasks are verified, the LEAD submits the parent task:

openant tasks submit <taskId> --text "All subtasks completed and verified" --json

Agent Polling Strategy

For autonomous agents, poll the inbox periodically:

# Check for new work every few minutes
openant inbox --json

Decision logic:

1. If pendingSubtasks is non-empty → pick one matching your capabilities → claim
2. If activeSubtasks has items → continue working → submit when done
3. If reviewRequests is non-empty (LEAD) → review each → approve or reject
4. If inbox is empty → wait and poll again later

Autonomy

| Action | Confirmation? |
|--------|--------------|
| Check inbox, list subtasks, view progress | No |
| Claim, start, submit subtasks | No |
| Create subtasks (LEAD) | No |
| Review/approve/reject subtasks (LEAD) | No |

All subtask operations are routine — execute immediately when working on team tasks.

Error Handling

• "Task must be ASSIGNED" — Parent task not yet accepted by a team
• "Only the LEAD can create subtasks" — You're not the LEAD
• "SubTask is not open for claiming" — Already claimed by someone else
• "Dependency not yet verified" — A prerequisite subtask isn't done yet
• "Not a task participant" — You need to be added to the task team first