Menu

Individual skill

pl-dispatch

0upvotes

PL (Project Lead) role sub-skill for opening and scheduling journeys. Loaded ONLY through the pl core routing table; NEVER auto-load from context, never invoke directly.

skills/T-delegation-and-work-orders/pl/skills/pl-dispatch/SKILL.md

Read pinned source

Source commit 1ca8a66158bc9ca26c288c6d5e7ebcf2ffb8491a

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Network or broad shell
Last checked
Nov 10, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
864
Repository last updated
Nov 4, 2026
License
Apache-2.0

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# PL · Dispatch — opening and scheduling journeys

Scripts named below run as `bash "${PL_SKILL_DIR}/scripts/<name>.sh" ...`, where `PL_SKILL_DIR` is the
absolute path of the `pl` skill directory; set it in the same Bash call. When you write text that an
executor will read, the executor has no `PL_SKILL_DIR`: substitute the absolute path of the pl skill's
`scripts` directory for `<PL_SKILL_DIR>` when you write the dispatch.

Sub-skill of the PL role. The pl core skill invokes this EXPLICITLY when a new
journey opens (the owner asks for a dispatch prompt or to open work; "owner" means whoever owns the work,
often the user), when scheduling is decided (what's next / what to schedule while the owner is away),
or when parallelism/capacity is in question. Core iron rules bind unchanged: never write product code;
never trust report prose — disk over words; the owner is addressed in the user's own language, while
agent-to-agent text uses the project's working language (English by default). Canonical scripts:
the pl skill's `scripts/`; canonical references: the pl skill's `references/`. The workspace layout
Back to top