agent-team-sync-check

To check agent inbox messages and task dependencies, run a sync check using the CLI with the required --agent parameter, optionally including --run and --task, to return structured data fields highlighting unread messages, blocking issues, and warnings.

An agent team sync check is used in workflow orchestration to identify unresolved inbox messages and incomplete task dependencies for a specified agent, preventing stalled work and ensuring readiness to proceed across all workflows or individual tasks.

Yes, you can limit a dependency and inbox check to a specific run or task by passing the --run and --task flags along with the required --agent parameter, enabling targeted validation instead of scoping across all workflows.

Checking for agent blockers returns structured data fields including data.sync.blocking, data.sync.unread_messages, data.sync.issues, and a top-level warnings field to surface incomplete dependencies and inbox messages.

Yes, you need to specify an agent when validating workflow readiness because the --agent parameter is required by the CLI to scope the inbox and dependency check, while --run and --task remain optional filters.