What problem does it solve? When an agent is about to fan out work across subagents, it often defaults to parallelism without checking whether any unit will publish commits, PRs, tags, merges, or deploys. This Skill prevents unreviewed publishing swarms by forcing an explicit routing decision before any fan-out happens. ## Core Features & Use Cases - Output-based routing: Classifies each unit's declared output as publishing (commit, pull_request, tag, merge, deploy, durable_artifact) or non-publishing (report, research, review, verification) and routes accordingly. - Three deterministic routes: Returns local, delegate_invoker, or subagent_fanout with concrete handoff steps for each route. - Executable decision script: A Node.js CLI validates work kinds and outputs, exiting non-zero on undeclared or unknown outputs. - Use Case: Before spawning eight subagents for a separable refactor, run the routing check; if any unit produces a commit or PR and Invoker MCP tools are available, the work is submitted to Invoker's persisted task graph instead of an unsupervised swarm. ## Quick Start Ask the agent to run the route-delegation check with the available tools, work kind, and declared outputs before spawning any subagents.
