convoy-management
Convoy Management organizes multi-agent work in Gas Town by creating convoys of related beads as primary work orders, decomposing goals into persistent beads and ephemeral wisps, assigning tasks to long-lived Crew or transient Polecats, tracking progress through hooks and heartbeats, and landing completed convoys through branch merges. Use this when coordinating parallel distributed work across multiple agents or tracking progress of complex multi-step efforts requiring quality verification before completion.
git clone --depth 1 https://github.com/a5c-ai/babysitter /tmp/convoy-management && cp -r /tmp/convoy-management/library/methodologies/gastown/skills/convoy-management ~/.claude/skills/convoy-managementSKILL.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 1. **Create convoy** from goal or MEOW decomposition 2. **Decompose** into beads (persistent) and wisps (ephemeral) 3. **Assign** beads to Crew (long-lived) or Polecats (transient) 4. **Track** progress via hooks and heartbeats 5. **Verify** all beads complete with quality checks 6. **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`
Review TypeScript code changes for consistency, type safety, and monorepo patterns across babysitter packages
Generate and validate documentation for @a5c-ai/babysitter-sdk CLI commands and exported APIs
Scaffold new babysitter process definitions following SDK patterns, proper structure, and best practices. Guides the 3-phase workflow from research to implementation.
Architect code review with DRY, YAGNI, abstraction, and test coverage principle enforcement