---
name: humanlayer-subagent-orchestrator
description: "orchestrate sub-agents to accomplish complex long-horizon tasks without losing coherency by delegating to sub-agents"
license: "Apache-2.0"
metadata:
  decimalai-skill-id: "4bce5ff2-75d1-4721-8ef8-ef7416b3dc6e"
  decimalai-version-id: "9285b181-7e29-405d-90ba-a0c43b7d0af1"
  decimalai-version: "1"
  decimalai-body-sha256: "33330297e3d804899832a484786ee2859bd914afb000ad4ea2a7f3c6b1d72b5c"
  decimalai-name: "humanlayer/subagent-orchestrator"
  decimalai-format: "1"
  decimalai-invocation: "model"
  decimalai-category: "agent-tooling"
  decimalai-source: "https://app.decimal.ai/s/humanlayer-subagent-orchestrator@1/SKILL.md"
---
This skill provides you with **CRITICAL** instructions that will help you to maintain coherency in long-horizon context-heavy tasks. 

You have a large number of tools available to you. The most important one is the one that allows you to dispatch sub-agents: either `Agent` or `Task`. 

All non-trivial operations should be delegated to sub-agents. You should delegate research and codebase understanding tasks to codebase-analyzer, codebase-locator and pattern-locator sub-agents. 

You should delegate running bash commands (particularly ones that are likely to produce lots of output) such as investigating with the `aws` CLI, using the `gh` CLI, digging through logs to `Bash` sub-agents. 

You should use separate sub-agents for separate tasks, and you may launch them in parallel - but do not delegate multiple tasks that are likely to have significant overlap to separate sub-agents.

IMPORTANT: if the user has already given you a task, you should proceed with that task using this approach. 

If you have not already been explicitly given a taks, you should ask the user what task they would like for you to work on - do not assume or begin working on a ticket autoatically.