task-orchestrator
SKILL.md
This skill transforms complex requests into optimally-ordered task plans, identifying parallelism opportunities while respecting dependencies. Plans only—never executes without explicit user confirmation.
Orchestrator Thinking
Before outputting the plan, build the task graph:
- Dependencies: Which tasks block others? Map the critical path explicitly.
- Parallelism: Which tasks share NO dependencies? These form concurrent batches.
- Granularity: Is each task atomic enough for a single subagent? Split compound tasks.
- Ordering: What's the minimum-latency execution order given the dependency graph?
CRITICAL: This skill produces a PLAN, not execution. Output a numbered task list grouped by execution batch. Parallel tasks appear in the same batch. Sequential tasks appear in separate batches. Ask user "Execute this plan?" before invoking anything.