subagent

To enforce a strict git commit and push workflow for delegated tasks, apply a disciplined execution protocol that mandates pulling first, planning, executing, verifying, and pushing changes to the remote. This ensures traceability and hygiene.

A pull-first execution protocol for multi-agent task delegation is a rigid workflow where subagents pull remote changes before parsing tasks, gathering context, and planning. It ensures state alignment and traceability across complex projects.

To divide complex projects among multiple agents, use task-scoped delegation by providing a task brief and clear acceptance criteria. The subagent then follows a structured parse, plan, execute, and verify workflow to complete and push changes.

Your multi-agent environment lacks traceability after delegated task execution if it does not enforce a rigid protocol requiring commits, pushes, and backlog synchronization. Proper hygiene ensures changes are documented and remote state stays aligned.

Subagent task delegation requires a Tech Lead to provide a task brief and acceptance criteria. Without this initial input, the execution protocol cannot parse the task, gather context, or verify the completed work against expected standards.

The limitation of using rigid execution protocols for task management is the mandatory overhead of completing every step from pull to report. This strict sequence may slow down simple tasks that do not require full context gathering or remote pushes.