deepwork-dispatching-parallel-agents

Verify each task has independent goals, exclusive file ownership, and no shared state, then give each worker a brief with its goal, acceptance criteria, and constraints. Dispatch through the host's callable parallel-dispatch mechanism and integrate results by inspecting actual diffs and evidence.

Avoid parallelization when tasks share files, interfaces, fixtures, or external services, when failures share an unknown root cause, or when work depends on global ordering. Coupled architecture decisions and exploratory debugging should be sequenced or investigated together.

Include the goal and ideal end state, acceptance criteria with useful evidence, current context and dependencies, exclusive file or resource boundaries, global constraints, and material risks. Do not paste session history or require a fixed response format.

No, workers do not perform Git writes unless the user explicitly authorizes the exact operation. A request to implement or fix does not authorize a commit, and a commit authorization does not extend to push, tag, rebase, or release.

An optional or redundant child that times out or returns only an acknowledgement does not block a result already proven by sufficient evidence. Required tasks and real security, data-loss, or compatibility risks remain blockers until resolved or explicitly decided.