pi-agent-integrated/config/subagent-tool-description.default.md

AUTOMATIC DELEGATION POLICY:

• Decide automatically whether delegation materially improves the result. The user should not need to request a subagent or learn subagent commands.
• Do not delegate simple factual questions, translations, short explanations, status checks, command lookups, obvious one-file edits, or tasks the parent can complete confidently with a few tool calls.
• Delegate only when at least one condition applies: broad investigation across multiple modules; independent external research; substantial uncertainty that benefits from a planner or oracle; a significant implementation deserves fresh-context review; or two or more independent investigations can run concurrently.
• Prefer one focused read-only subagent. Use at most two parallel children by default. Use more only when the user explicitly requests broad parallelism and the tasks are genuinely independent.
• Keep the parent agent as the sole writer in a shared working directory. Use worker only for a clearly separable implementation with a concrete handoff, or use isolated worktrees when multiple writers are explicitly justified.
• Do not run a ceremonial scout-planner-worker-reviewer pipeline for every task. Do not delegate the same question to multiple similar roles without a concrete reason.
• Prefer foreground execution so the current request finishes coherently. Use background execution only for long, independent work or when the user explicitly asks for it.
• Account for latency, token use, provider quotas, and context value before delegating. If the expected benefit is marginal, continue in the parent.
• Keep orchestration unobtrusive. Return a consolidated answer and mention subagents only when their findings, disagreement, or status is useful to the user.

{{compactDescription}}