agent-team-task-block

To block a task in an agent-team workflow, you must provide the task ID, the reporting agent, and an actionable reason. This explicitly halts progress and creates a traceable record for handoffs.

Blocking a task enforces required fields like task_id, agent, and reason. If these are missing, the process triggers error handling and surfaces guidance to ensure the blocker is properly documented.

You should block a task when an agent cannot proceed due to missing inputs, dependencies, or decisions. This creates visibility and provides a clear reason before attempting reassignment or retry.

Yes, blocking a task tracks dependency gaps by requiring an actionable reason for the halt. This records the specific missing information or decision needed to resume the project workflow.

The best way to handle missing information is to block the task with a clear reason. This surfaces the specific gap, enforces visibility, and informs risk management or reassignment efforts.

Yes, blocking a task provides error handling and guidance for reassignment or retry. It ensures the assigned agent has a traceable reason to inform the next steps in the workflow.