Babysitter convoy-management

Create, track, and land convoys of related beads as primary work orders in the Gas Town multi-agent orchestration framework.

install

source · Clone the upstream repo

git clone https://github.com/a5c-ai/babysitter

Claude Code · Install into ~/.claude/skills/

T=$(mktemp -d) && git clone --depth=1 https://github.com/a5c-ai/babysitter "$T" && mkdir -p ~/.claude/skills && cp -r "$T/library/methodologies/gastown/skills/convoy-management" ~/.claude/skills/a5c-ai-babysitter-convoy-management && rm -rf "$T"

manifest: library/methodologies/gastown/skills/convoy-management/SKILL.md

Convoy Management

Overview

Manage the full lifecycle of Gas Town convoys: creation from a goal, bead decomposition, agent assignment, progress tracking, and landing (merge). Convoys are the primary work-order unit wrapping related beads.

When to Use

Starting a new multi-agent work effort
Coordinating parallel bead execution across agents
Tracking progress of distributed work
Landing (merging) completed convoy results

Process

Create convoy from goal or MEOW decomposition
Decompose into beads (persistent) and wisps (ephemeral)
Assign beads to Crew (long-lived) or Polecats (transient)
Track progress via hooks and heartbeats
Verify all beads complete with quality checks
Land convoy by merging bead branches

Key Concepts

Convoy: Primary work-order wrapping related beads
Bead: Git-backed atomic work unit (issue/task)
Wisp: Ephemeral bead destroyed after successful run
GUPP: If there is work on your Hook, YOU MUST RUN IT

Agents Used

```
agents/mayor/
```
- Creates and coordinates convoys
```
agents/crew-lead/
```
- Persistent collaborator on beads
```
agents/polecat/
```
- Transient worker for individual beads

Tool Use

Invoke via babysitter process:

methodologies/gastown/gastown-convoy