What problem does it solve? Deciding when and how to delegate work to subagents is error-prone: over-delegation wastes effort, under-specified prompts produce unusable results, and parallel writers collide in a shared checkout. This Skill provides a decision gate and dispatch patterns for routing independent work through the Agent tool in Claude Code or Pi. ## Core Features & Use Cases - Delegation Gate: A six-step check (direct-work, independence, context, write-conflict, verification, fan-out) that decides between direct work and N agents before any dispatch. - Dispatch Patterns: Foreground agents, parallel background agents, worktree-isolated editing agents, custom role briefs, and coordinator-managed role cohorts for multi-specialist deliverables. - Verification Contract: Treats agent completion messages as claims, requiring diff inspection, test runs, and evidence checks before synthesis. - Use Case: When implementing a cross-layer feature, dispatch API, UI, and test work to separate worktree-isolated agents after interfaces are defined, then verify each diff and synthesize the results. ## Quick Start Ask the agent to evaluate whether the current task should be handled directly or fanned out to parallel background agents, then dispatch and verify the results.
