Agent skill · posthog
subagent-orchestration
How and when to delegate work to subagents via the `subagent` tool (Explore, Plan, General). Use when a task involves codebase recon, implementation planning, or actual code changes that would benefit from an isolated context window instead of doing it all inline.
What it needs
About 4k tokens when loaded.
What this skill does
Subagent Orchestration You (the parent session) can delegate scoped work to focused subagents, each running in its own isolated Pi session with its own context window. Use this to keep your own context clean and to parallelize independent work. When to delegate Delegate when a piece of work is: Self-contained: it doesn't need your full conversation history, just a task and some context you can state explicitly. Isolable: it would otherwise burn a lot of your context window (e.g. broad codebase search, reading many files) for a result you can summarize down to a few paragraphs. Parallelizable: several independent instances of it can run at once (e.g. exploring two unrelated areas of a large codebase in the same turn). Do not delegate trivial one-line changes, or work that fundamentally needs your full conversation context to do correctly — that's what context (below) is for, but if almost everything is relevant, delegation adds overhead for no benefit. Bundled agents Agent Use for Tools Model Notes ------- --------- ------- ------- ------- Explore Focused, read-only recon: find files, entry points, data flow read, bash, grep, find, ls Sol, falls back to your current model Reports compressed findings, never edits Plan Turn Explore's findings (or your own) into a concrete implementation plan read, bash, grep, find, ls Inherits your current model Never edits General Actual implementation: make the code changes an Explore/Plan investigation identified, or any task that needs real edits read, bash, edit, write, grep, find, ls Inherits your current model Same read-write capability as you have; makes real changes Explore and Plan are read-only. General has the same read-write capability you do — reach for it when a change is mechanical/independent enough to delegate (especially several at once via parallel mode) rather than doing every edit yourself in sequence. For a small, one-off change, just make it directly instead of delegating. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills posthog/subagent-orchestration--6cea98