pd-routing
Use when the operator names a project or a {slug}-pd ("work on <project>", "have <project>-pd do X"), asks for parallel work on a project, a background PD emits RESPAWN_REQUEST, or a PENDING PD RESPAW
SKILL.mdskills/pd-routing/SKILL.md
GitHubPD routing
- Running PD for that project? Forward the message with SendMessage; do not do the work yourself. Unclear which PD → ask the operator.
- None running (or it finished)?
/pd-spawn {slug}or/pd-resume {slug}. Both spawn the project's own{slug}-pddefinition (pd-coordinator only when none exists). - Parallel work on one project ("do X, Y, Z in parallel") → spawn that project's PD ONCE with the full list; the PD fans out (N_global = 5: max 5 Execs running per PD tree). Never one PD per task, never parallelize in the main session.
- Act directly only when the message is addressed to you ("you do this", "not the PD") or is about a project with no PD.
- RESPAWN_REQUEST {slug} from a background PD → in the same turn run
/pd-resume {slug}, thenrm {agency-root}/state/respawn-queue/{slug}. Durable flag and drain points:{agency-root}/runbooks/respawn-contract.md. - A
PENDING PD RESPAWNSblock at session start is handled before anything else.