Foreman

Builder lanes

Many hands, one foreman

Independent tasks go to builder subagents, each in its own git worktree with a brief that says exactly what to build, how to test it and what not to touch.

Builder lanes merged per dayEach lane is one task built in its own git worktree, reviewed, then merged.
02244668810-0210-0310-0410-0610-082026-10-09 · lanes: 1510-092026-10-14 · lanes: 1010-142026-10-15 · lanes: 2010-152026-10-16 · lanes: 8610-1610-1710-20
Show the numbers
daylanes
2026-10-020
2026-10-030
2026-10-040
2026-10-060
2026-10-080
2026-10-0915
2026-10-1410
2026-10-1520
2026-10-1686
2026-10-170
2026-10-200
Subagents launched, by kindBuilders work in worktrees, reviewers read diffs, recon answers questions.
fm-builderfm-builder: 224224fm-reviewerfm-reviewer: 148148general-purposegeneral-purpose: 7676fm-reconfm-recon: 7171ExploreExplore: 88claude-code-guideclaude-code-guide: 77
Show the numbers
value
fm-builder224
fm-reviewer148
general-purpose76
fm-recon71
Explore8
claude-code-guide7

From brief to merge

  • Brief. fm lane brief ID writes the contract: the base commit, test first, the files it may change, the defects reviewers keep finding.
  • Review. An independent reviewer reads the branch; findings go back to the builder.
  • Merge. fm lane merge runs the task's criteria first and refuses a red branch.
  • Resume. A stopped session picks its lanes back up.

Next: Drive and headless