---
id: 3227a923-84c4-4fe3-8574-dbf74d6e8b37
type: workflow
title: "Agent swarm workflow for parallel Rust implementation tasks"
tags: [sba-scout, rust, swarm, claude-code, workflow, parallelism, agent, tmux]
importance: 0.5
confidence: 0.8
created: "2026-02-27T01:18:38.159503+00:00"
updated: "2026-02-27T01:18:38.159503+00:00"
---

# Agent Swarm Workflow for Parallel Rust Implementation

## Context
Used during SBA Scout Rust rewrite Phase 1 to parallelize implementation across multiple files.

## Workflow Pattern

1. **Create team** — spin up tmux-backed swarm with named agents
2. **Create tasks with dependencies** — map out which tasks are unblocked vs. blocked
3. **Fan out unblocked tasks** to `swarm-coder` agents (bypassPermissions mode)
4. **Send completed work to `swarm-reviewer` agents** for code review
5. **Fix issues found by reviewers** before proceeding
6. **Dispatch newly-unblocked tasks** after dependencies complete

## Critical Rule: File Contention

When multiple tasks write to the **same file** (e.g., all query functions going into `queries.rs`), batch them into **one coder agent** to avoid merge conflicts.

Tasks touching **different files** (e.g., `main.rs` vs `queries.rs` vs `schema.rs`) can safely run in parallel.

## Agent Configuration
- Model: Sonnet (per Cal's preference for sub-agents)
- Mode: `bypassPermissions` for coder agents
- Reviewer agents: separate agent instances, no bypass needed

## Outcome
Phase 1 completed faster than sequential implementation. Reviewer caught a missing `UNIQUE` constraint on `lineups.name` that was fixed before commit — review step proved valuable.

## Applicable Projects
Any multi-file Rust (or other language) implementation where tasks can be decomposed by file/module ownership.