orchestrator
Skill88 starsChanged 8 months agoMITView on GitHub
Split complex tasks into sequential steps with parallel subtasks. Use for multi-step workflows needing dependency ordering and adaptive planning.
85 other projects use a version of this.
Adopted by
Most recently taken up by
- VinayKhandia/no-sloptheir own version, first seen Nov 15, 2026
- PedroMeloOfficial/Study-Agent-Matrixtheir own version, first seen Nov 15, 2026
- taniwhaai/skillstheir own version, first seen Nov 15, 2026
- scottconverse/productteamtheir own version, first seen Nov 15, 2026
- Fili999/ai-hubtheir own version, first seen Nov 15, 2026
- ozgureyilmaz/skillstheir own version, first seen Nov 10, 2026
Used with
Projects with it also use worker, reviewer and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
stotihvSkillworker
Execute beads autonomously within a track. Handles bead-to-bead context persistence via Agent Mail, uses preferred tools from AGENTS.md, and reports progress to orchestrator.
Also in 3 projects that use this
MicrosoftSkillreviewer
ASP.NET Core ハンドブックの記事をレビューする。Use when: 記事をレビューする、ドキュメントを校正する、コードレビューする、PRをレビューする。技術ドキュメントのレビュー、品質チェック、校正。
Also in 4 projects that use this
am-willSkillplanner
Create comprehensive, phased implementation plans with sprints and atomic tasks. Use when user says: "make a plan", "create a plan", "plan this out", "plan the implementation", "help me plan", "design a plan", "draft a plan", "write a plan", "outline the steps", "break this down into tasks", "what's the plan for", or any similar planning request. Also triggers on explicit "/planner" or "/plan" commands.
Also in 4 projects that use this
yakatotechSkilladvisor
Provide improvement suggestions and advice on work content. Use for document review, efficiency suggestions, and best practices
Also in 3 projects that use this
AWSSkillplanning
Discovers user intent and generates a structured, step-by-step plan for model customization workflows. This skill must always be activated alongside any other skill when the user's request relates to model customization — including fine-tuning, training, building, customizing, reviewing data, or getting advice on approach, regardless of domain. Do not skip this skill even if the immediate ask is narrow (e.g., reviewing data format or a single workflow step), because planning discovers the full scope of work needed. Also activate when the user wants to resume, continue, or modify an existing plan.
Also in 3 projects that use this
OpenAISkillobservability
Vercel Observability expert guidance — Drains (logs, traces, speed insights, web analytics), Web Analytics, Speed Insights, runtime logs, custom events, OpenTelemetry integration, and monitoring dashboards. Use when instrumenting, debugging, or optimizing application performance and user experience on Vercel.
Also in 3 projects that use this
Other versions85 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 85
- nubjs/nub★ 4.4ksame name
- SirAllap/agentglass★ 348same name
- DylXBT/claude-orchestrator-skills★ 114same name
- nahisaho/MUSUBI★ 74same name
- olivieropinotti/orchestrator-skill★ 70same name
- sanky369/vibe-building-skills★ 30same name
- felvieira/claude-skills-fv★ 28same name
- robertbstillwell/marketing-skills★ 26same name
- kcns008/cluster-agent-swarm-skills★ 25same name
- maroffo/claude-forge★ 17same name
75 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository8 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- bug-fixSkill
- deploy-checkSkill
- dev-setupSkill
- pre-release-checkSkill
- qa-pipelineSkill
- refactor-analysisSkill
- refactorSkill
The file
We split this skill into the rules it gives an agent
7 rules. 0 are common, 7 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 71 edited versions we read keep these.
7
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 24
Wait for all subtasks in current step to complete
- Distinctive: line 30
Add, remove, or modify subtasks as needed
- Distinctive: line 34
Use synthesized results as context for next step
- Distinctive: line 39
After each step, explicitly reconsider:
- Distinctive: line 43
Should we add new validation steps?
- Distinctive: line 53
Always start with a single analysis task to understand full scope
- Distinctive: line 56
Use TaskCreate/TaskUpdate to track steps and subtasks
“Common” is measured: kept by at least 6 in 10 of the 71 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Orchestrator
Split the following task into sequential steps with parallel subtasks: $ARGUMENTS
Process
1. Initial Analysis
- Analyze the entire task scope and requirements
- Identify dependencies and execution order
- Plan 2-4 sequential steps based on dependencies
2. Step Planning
- Each step can contain multiple parallel subtasks
- Define what context from previous steps is needed
- Request concise summaries (100-200 words) from each subtask
3. Step-by-Step Execution
- Execute all subtasks within a step in parallel using Agent tool
- Wait for all subtasks in current step to complete
- Pass relevant results to next step
4. Review and Adapt After Each Step
- Validate if remaining steps are still appropriate
- Adjust next steps based on discoveries
- Add, remove, or modify subtasks as needed
5. Progressive Aggregation
- Synthesize results from completed step
- Use synthesized results as context for next step
- Build comprehensive understanding progressively
Adaptive Planning
After each step, explicitly reconsider:
- Are the next steps still relevant?
- Did we discover something requiring new tasks?
- Can we skip or simplify upcoming steps?
- Should we add new validation steps?
Initial Plan: Step 1 -> Step 2 -> Step 3 -> Step 4
After Step 2 (no errors found): Skip Step 3 -> Simplified Step 4
After Step 2 (critical issue): -> New Step 2.5 -> Modified Step 3Guidelines
- Always start with a single analysis task to understand full scope
- Group related parallel tasks within the same step
- Pass only essential findings between steps (summaries, not full output)
- Use TaskCreate/TaskUpdate to track steps and subtasks
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

