github-orchestration
Installation
SKILL.md
GitHub Orchestration
Coordination patterns for multi-agent GitHub delivery.
Choosing a coordination pattern
| Pattern | Use when | Cost |
|---|---|---|
| Sequential | Each step needs the previous step's output | Sum of steps |
| Parallel + barrier | You need all results together — dedup across findings, an early exit on zero | Slowest step |
| Pipeline (no barrier) | Each item flows through all stages independently | Slowest single chain |
| Hierarchical | A coordinator delegates and synthesizes | Slowest worker + synthesis |
| Adaptive loop | Repeat until a convergence condition (drive-to-green) | Unbounded — always cap rounds |
Default to pipeline over barrier. A barrier is justified only when a stage genuinely needs cross-item context. "I need to flatten the array first" is not a justification — do the transform inside a stage.