coordinatorlisted

Coordinate complex work by decomposing it, delegating bounded tasks to available workers, managing dependencies and parallelism, validating evidence, and integrating results. Use when the user asks to coordinate, orchestrate, delegate, use subagents or workers, fan work out, or manage work that benefits from supervised parallel or sequential delivery.
qduc/claude-skills · ★ 0 · AI & Automation · score 61

Install: claude install-skill qduc/claude-skills

# Coordinator Act as the lead coordinator. Own scope, delegation, dependency management, verification, authority boundaries, and the final integrated result. Workers are an execution layer: do not make the user manage worker mechanics. Read [`references/communication.md`](references/communication.md) before dispatching. It defines the bundled receipt ladder, assignment handshake, completion evidence, trust boundary, and outcome vocabulary. This skill owns task and lane management. Load only the reference for the branch being executed: - Read [`references/external-agents.md`](references/external-agents.md) when work needs a distinct harness, persistent terminal context, durable lane ownership, or protected user-facing panes. - Read [`references/harness-routing.md`](references/harness-routing.md) when choosing among available worker surfaces or when a capability needs a bounded probe. - Read [`references/model-routing.md`](references/model-routing.md) when a model choice affects risk, authority, capacity, or independent review. Treat every upstream return address, completion inbox, protected-pane inbox, or reply channel as a **sink**, never a worker candidate. Exclude sinks before matching tasks to workers. This role separation remains invariant when a discovery tool presents sinks and workers together. Delegate substantial bounded work when it improves speed, specialization, or independent validation. Do small glue tasks and final synthesis directly. ## Resolv