coordinate-handoffs

To validate sub-agent handoff artifacts, you verify the structure and content of output files from planning, implementation, and QA agents against defined artifact schemas. This ensures deterministic workflow progression by confirming successful phase completion.

Managing retry logic for failed AI agent tasks involves checking validation results against configured retry limits. If an artifact fails validation, the workflow automatically triggers a retry for the sub-agent task before escalating persistent issues.

Orchestrating phase transitions requires sequencing workflow steps based on artifact validation. If a generated report is valid, the workflow proceeds to the next phase; if not, it either retries the task or escalates the issue.

You should escalate persistent sub-agent failures when automatic retries exceed defined retry limits. Escalation manages complex issues by routing persistent workflow stagnation or incorrect execution to human oversight.

No, coordinate-handoffs requires adherence to defined artifact schemas and retry limits for deterministic workflow progression. Schema validation is the core mechanism for verifying output structure and managing phase transitions.

Multi-agent workflow stagnation occurs when implementation output fails artifact validation, preventing phase progression. Sequencing logic determines whether to retry the sub-agent, escalate the issue, or proceed to QA.