Delegate a bounded task when another agent can make progress independently. Decide where the work belongs before starting the agent, because placement controls ownership, worktrees, and issue history.
Choose the work shape
Match the delegated task to one of these placements:
Add a reviewer to the current issue
Spawn another session on the same issue for bounded review:
Use this shape for read-only review or other work that does not need concurrent edits in the same checkout.
Create required implementation work
Create and start a child issue in one command:
--start already creates the worktree and agent. Do not follow it with podium agent spawn for the same child.
File discovered work for later
To record useful work that the current issue can ship without, stay on the current issue and create a top-level proposal:
Do not claim, start, or stage the proposal for another agent. If you are explicitly moving this session onto the new work instead, use podium issue attach --spinoff "Cache telemetry cleanup" --confirm-rehome; that command creates the top-level issue and relationship before rehoming the session.
Track a running child
Use the child issue or session identifier to read its state:
await has a bounded timeout and reports current status when the child is still working.
Send cross-agent context
Address durable coordination to the issue unless one specific session must receive it:
Add --expect-response only when you need a reply. Use interrupt urgency only when continuing would waste work or create a conflict.
Podium does not serialize agents editing one worktree. Give each concurrent implementation its own issue and worktree, or assign explicit file ownership before both sessions edit.
podium lock acquire resource_name --wait. A lease expires and does not enforce access, so it works only when every participant uses the same lock. Use podium merge-lock for branch merges rather than inventing another merge lock name. 
