orchestrating-parallel-research
/orchestrating-parallel-research
Koordynuje równoległe zadania badawcze lub funkcjonalne w izolowanych przestrzeniach agentów: dzieli pracę, izoluje, rozsyła i raportuje, np. eksperymenty na zdalnych GPU.
- Autor
- babyGao ↗
- Repozytorium
- agent-pilot-skills ↗
- Licencja
- MIT
- Ostatnia zmiana repozytorium
- 05.09.2026
Ocena i bezpieczeństwo
- Pliki w paczce
- 5
- Skrypty
- 0
- Komentarze HTML
- 0
- Adresy URL w SKILL.md
- 0
Brak sygnałów. Repozytorium zmienione 05.09.2026, bez odwołań do wycofanych modeli i API.
MIT, otwarta: można używać i zmieniać, z zachowaniem informacji o autorze.
Co robi i kiedy
Koordynuje równoległe zadania badawcze lub funkcjonalne w izolowanych przestrzeniach agentów: dzieli pracę, izoluje, rozsyła i raportuje, np. eksperymenty na zdalnych GPU.
Oryginalny opis (EN)
Use when running many independent tasks in parallel across isolated agent workspaces — fanning out research experiments (remote GPU, ablations, innovation points) or feature work — and you act as the coordinator deciding how to split, isolate, dispatch, and report.
Jak działa
- Overview
- When to Use
- The four coordinator moves
- Standardize before you launch
- Common Mistakes
- Verification (you, deterministically)
Podgląd SKILL.md
---
name: orchestrating-parallel-research
description: Use when running many independent tasks in parallel across isolated agent workspaces — fanning out research experiments (remote GPU, ablations, innovation points) or feature work — and you act as the coordinator deciding how to split, isolate, dispatch, and report.
---
# Orchestrating Parallel Research
## Overview
You run a fleet of agents as the **coordinator (军师), not a worker**. Your leverage is deciding *what to split, how to isolate, what to hand each agent, and how to synthesize* — never doing the grunt work yourself.
**Core principle:** front-load the standardization (directories, isolation, dispatch contract) so N agents run at once without colliding — then observe and adjust. It is a standing engineering setup decided **up front**, NOT mid-flight patching. Don't fix agent-1's layout at minute 10 then agent-2's at minute 20 — you predicted the situations and standardized before the first launch.
## When to Use
```dot
digraph when {
"≥2 independent tasks?" [shape=diamond];
"Shared state / tight sequence?" [shape=diamond];
"Do it yourself / sequential" [shape=box];
"Orchestrate: split → isolate → dispatch → observe" [shape=box];
"≥2 independent tasks?" -> "Do it yourself / sequential" [label="no"];
"≥2 independent tasks?" -> "Shared state / tight sequence?" [label="yes"];
"Shared state / tight sequence?" -> "Do it yourself / sequential" [label="yes"];
"Shared state / tight sequence?" -> "Orchestrate: split → isolate → dispatch → observe" [label="no"];
}
```
**Two modes** — pick per project:
- **(A) Local software dev (most common)** — agents modify/build a software project locally; isolate via git branch/worktree.
- **(B) Research experiments** — remote GPU, many agents, parallel runs (implement / tune / ablate / main run / summarize); isolate via full-folder checkout. You read papers → define innovation points → hand each an outline/pseudocode.
**Don't** orchestrate a single task, tightly-coupled sequential steps, or anything trivial — do it yourself.
## The four coordinator moves
1. **Split on isolation boundaries** — cut the work so no two agents touch the same files (one module / package / innovation point each). Getting the cut right up front is what prevents merge pain later.
2. **Isolate physically** — each agent gets its **own full workspace** (fresh checkout of the main branch) + own branch + own artifact dir, **local and remote**. Edits and outputs can't cross-contaminate. Merge-back is optional. → [references/isolation-and-dirs.md](references/isolation-and-dirs.md)
3. **Dispatch direction, not a cage** — hand each agent clear **input / output / goal + an outline or pseudocode**, then let it implement. Do NOT script every step or pile on "don't do X"; let it think. → [references/dispatch.md](references/dispatch.md)
4. **Observe & adjust** — read each report, evaluate against the goal, re-plan the next wave. Whether an agent complied or produced something different is *your* signal to steer. Dynamic scheduling, not fire-and-forget.
## Standardize before you launch
| Pillar | Rule | Detail |
|---|---|---|
| Directory | Trunk fixed forever; each new point = a new subfolder, never edit the trunk | [isolation-and-dirs.md](references/isolation-and-dirs.md) |
| Isolation | One full workspace per agent, local + remote, no cross-pollution | ↑ same |
| Remote GPU / SSH | One serial SSH channel; thin files back, heavy artifacts stay; deploy + gate checklist | [remote-gpu-ssh.md](references/remote-gpu-ssh.md) |
| Dispatch | Direction + pseudocode; agents self-test; you don't hand-test | [dispatch.md](references/dispatch.md) |
| Reporting | Readability first: effect/analysis not code, tables + one-line takeaway, split if >~4000 chars | [reporting.md](references/reporting.md) |
## Common Mistakes
**❌ Micromanaging** the agent step-by-step → **✅** give goal + pseudocode, let it implement.
**❌ Mid-flight standardizing** (patch each agent's layout as you go) → **✅** fix dirs/isolation/contract before the first launch.
**❌ Shared workspace** so agents clobber each other → **✅** one full workspace each, local + remote.
**❌ Doing the work yourself** "because it's faster" → **✅** you're the brain: split, dispatch, synthesize.
**❌ Fat reports** full of function/variable names → **✅** effect + analysis, tables, one-line conclusions.
**❌ Param grids / tuning on the shared GPU** → **✅** GPU only for first-run / one-off collection / final adjudication; grids go offline.
## Verification (you, deterministically)
Agent output must be checkable **without trusting its self-score**: diff its changes, re-run its claimed test, or run a deterministic check script. Also confirm (a) your project's own correctness contract still holds (whatever you defined — output-equivalence, quality parity, a golden result) and (b) the code path you switched on actually executed (**instrument a counter, count > 0**) — "it ran and matched" is meaningless if the new path never ran.
Pliki w paczce (5)
- SKILL.md 5 KB
- references/dispatch.md 3 KB
- references/isolation-and-dirs.md 2 KB
- references/remote-gpu-ssh.md 2 KB
- references/reporting.md 1 KB
Wersje
W bazie nie ma innych skilli o nazwie orchestrating-parallel-research.
Migawka bazy z 13.11.2026 · wersja paczki cdbb5cf4e7ac (skrót SHA-256 całej paczki)
Pobrania w ostatnich 30 dniach: 0 · ranking
Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.
Podobne skille
- 96parallel-slices
Koordynuje równoległą pracę w przestrzeniach Jujutsu: dzieli zmiany na części do przeglądu i prowadzi izolowane workspace'y. - 100delegate-work
Koordynuje równoległe subagenty, dzieli pracę, izoluje kontekst i unika konfliktów w plikach, a potem sprawdza wyniki. - 84parallel
Koordynuje równoległe agenty przy niezależnych zadaniach, dotykających różnych plików lub obszarów. - 100run-experiment
Wdraża i uruchamia eksperymenty ML na lokalnych lub zdalnych serwerach GPU i startuje zadania treningowe. - 100orchestrating-subagents
Prowadzi równoległe i szeregowe subagenty: koordynuje wykonanie planu z wielu jednostek, syntetyzuje wyniki niezależnych przebiegów i obsługuje awarie z ponowieniem. - 91orchestrating-swarms
Koordynuje wielu agentów Claude Code: równoległe przeglądy kodu, potoki z zależnościami i samoorganizujące się kolejki zadań.