Menu
orchestrate sub-agents to accomplish complex long-horizon tasks without losing coherency by delegating to sub-agents
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Baseado na classificação ocupacional SOC
Restate the last message in plain human language, with no jargon.
Give a capable engineer a concise briefing on the critical facts and implications of an effort before it is built or after it is completed. Use when the human explicitly invokes $facts, and never otherwise; do not invoke this skill automatically.
Vendor skills from a GitHub repository into this repo. Use when asked to import, vendor, list, add, or update skills from another skills repository while preserving provenance and detecting local edits.
Use when given a well-scoped bug fix or small feature ticket from Jira. Investigates the ticket, researches the codebase, proposes a fix, then plans and implements on approval. Lighter alternative to the full deep-work pipeline for tickets that don't need multi-session design discussion.
Use when starting work on a ticket that needs refinement before entering the deep-work pipeline. Reads from Jira, pasted text, or a file, then interactively refines it into a structured ticket.md.
Use when a session is ending and you want to analyze process efficiency. Triggers on requests to review how a session went, evaluate context usage, or identify workflow improvements.
| name | subagent-orchestrator |
| description | orchestrate sub-agents to accomplish complex long-horizon tasks without losing coherency by delegating to sub-agents |
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 task, you should ask the user what task they would like for you to work on - do not assume or begin working on a ticket automatically.
