subagent-delegation

Subagent delegation orchestrates I2 and I4 workflows by providing canonical contracts, payload structures, and multi-agent synchronization across Rails and React domains. It defines strict containment rules to minimize drift and ensure verifiability.

Direct-vs-delegate decision criteria help you choose between direct work and delegating to a subagent. The playbook provides specific guidelines to determine when delegation is appropriate based on task complexity and workflow requirements.

Recovery and post-join verification guidelines handle mid-flight failures during subagent delegation. The playbook defines pre-fork freezing lists and maxTurns budgeting to ensure safe recovery and verifiable results after parallel operations encounter issues.

Multi-domain parallel I4 review patterns mitigate risk through strict format and containment rules. The playbook defines canonical contracts and synchronization strategies to ensure safe parallel reviews across Rails and React domains without drift.

MaxTurns budgeting limits the operational scope of delegated subagents during I2 and I4 workflows. It prevents runaway processes by defining strict containment boundaries, ensuring verifiable results and minimizing drift across multi-agent synchronization.

Pre-fork freezing creates stable snapshot lists before dispatching subagents to ensure consistent execution states. This process minimizes drift and enables safe parallel reviews by locking the working environment before the fork-join operation begins.