PUBLIC · MANAGE WORKFLOWS

Plan delegation without agent sprawl

Give parallel work clear ownership and a reason to exist.

When to use it

When a task looks parallel and you are about to start several assistants at once.

What to expect

A decision: one agent, or a delegation plan with an owner, inputs, outputs, permitted files, and completion criteria per task, and how results are reconciled.

Example

Migrating three services to a new logging library while a release is being cut.

Add your context

Optional. Leave fields blank to copy a reusable template. What you type stays in this tab.

taskprojectlimitfiles or services

PROMPT TEMPLATE

Evaluate whether {{TASK}} benefits from delegation.

Context: {{PROJECT}}
Permitted concurrency: {{CONCURRENCY_LIMIT}}
Shared resources: {{SHARED_RESOURCES}}

Default to one agent when the work is tightly coupled. Delegate only bounded tasks that can run independently alongside useful primary work. For each proposed task, define owner, inputs, expected output, permitted files, dependencies, and completion criteria.

Prevent overlapping writes. Require agents to return findings and evidence, not create additional agents. Define how the primary agent will reconcile results and stop redundant investigation.

Return the smallest justified delegation plan, or explain why a single execution path is preferable. Do not start agents during this planning step.

4 of 4 context fields remaining.

Free to copy. Use it in the tools you already have.

← Back to the library