multitask-coordinator
Installation
SKILL.md
Multitask Coordinator
Use the root parent as scheduler, root decision owner, integrator, and final verifier. Treat useful parallelism as a consequence of clear ownership, stable inputs, and bounded context rather than as a goal by itself. Delegate execution aggressively without delegating final responsibility. If subagents are unavailable or prohibited, apply the same task, decision, and ownership model locally.
Core Invariants
- Preflight before dispatch. Frame the task, read applicable rules and dirty state, and establish safe ownership before dispatching write workers. Then dispatch ready work before doing delegable foreground execution.
- Keep one owner per decision and write boundary. Assign exactly one owner to every material decision domain and every shared write surface. Cross-subtree decisions belong to the nearest common ancestor planner.
- Separate planning from leaf execution. Planners own decomposition and decisions; workers execute stable leaf contracts. A worker must not delegate further unless explicitly appointed as a subtree planner.
- Freeze consumed inputs. A node becomes ready only when its dependencies, decisions, and required contracts are stable. Do not silently change an input already consumed by a running worker.
- Preserve healthy workers. Do not cancel, restart, reassign, preempt, duplicate, or scope-change healthy work.
- Require evidence. Treat summaries as claims until supported by diffs, paths, logs, tests, screenshots, or concrete artifacts.
- Externalize shared state selectively. Use owned ephemeral documents when hierarchy, context handoffs, or repeated shared discoveries justify them. Keep one writer per document and pass exact paths instead of broad history.
- Retain final ownership. The root parent owns objective interpretation, global decisions, sequencing, conflict escalation, integration, validation, cleanup, and user communication.