Parallel Agent

This is a thin local policy layer for Pi. It decides whether and how to split work; the installed pi-subagents skill is the source of truth for APIs, roles, execution controls, and detailed recipes.

Before dispatching

1. Read the installed pi-subagents skill completely.
2. Follow its router to the relevant reference: prompting/roles, execution controls, multi-lane orchestration, or constraints/recipes.
3. Run subagent({ action: "list" }) and use only executable, non-disabled, session-allowed agents; capability ceilings or allowlists can still reject a launch.
4. Do not invent or restate runtime behavior when the installed documentation already defines it.

Decide whether to parallelize

Parallelize only when each lane has a distinct problem domain and can proceed without another lane's result or shared mutable state. Typical cases include unrelated bugs, independent subsystem reconnaissance, separate review angles, or local context plus external research.

Do not parallelize a coupled investigation, dependent sequence, overlapping source seam, or tasks that would edit the same state. Understand the shared root cause first.

Local invariants