"Set up this repo so a small team of Claude Code agents can work in parallel without editing the same files. Copy the 5-table setup from Anthropic's 1,000-agent Fermat run:
1. Create .team/team.db (SQLite) with 5 tables:
- announce: the lead's orders to everyone
- assign: who owns which task
- notes: progress, questions and "I'm free" posts
- subtasks: the to-do list, with the files each task may touch. A task belongs to the first agent whose claim succeeds: UPDATE subtasks SET claimed_by = ? WHERE id = ? AND claimed_by IS NULL, then check that exactly one row changed
- landed: finished work, with the branch, the commit and whether the tests passed
2. Write 4 small scripts in .team/: claim, note, land and status, one command each.
3. Write .team/HELPER.md, the loop every helper follows: read announce, claim one task, work only in your own git worktree and branch, touch only that task's files, run the tests, merge into main only with green tests, log it in landed, post a note, claim the next task. If a task is too big, split it into new subtasks instead of giving up.
4. Write .team/LEAD.md: split the goal into subtasks, list the files each one may touch, never leave two open tasks on the same file, read notes every few minutes and move free helpers to whatever is stuck.
Don't start any agents. When it's ready, show me the files and the exact commands to start 1 lead and 3 helpers, each in its own git worktree."
Part 1: https://www.binance.com/square/post/387073609143735
3/3
1. Create .team/team.db (SQLite) with 5 tables:
- announce: the lead's orders to everyone
- assign: who owns which task
- notes: progress, questions and "I'm free" posts
- subtasks: the to-do list, with the files each task may touch. A task belongs to the first agent whose claim succeeds: UPDATE subtasks SET claimed_by = ? WHERE id = ? AND claimed_by IS NULL, then check that exactly one row changed
- landed: finished work, with the branch, the commit and whether the tests passed
2. Write 4 small scripts in .team/: claim, note, land and status, one command each.
3. Write .team/HELPER.md, the loop every helper follows: read announce, claim one task, work only in your own git worktree and branch, touch only that task's files, run the tests, merge into main only with green tests, log it in landed, post a note, claim the next task. If a task is too big, split it into new subtasks instead of giving up.
4. Write .team/LEAD.md: split the goal into subtasks, list the files each one may touch, never leave two open tasks on the same file, read notes every few minutes and move free helpers to whatever is stuck.
Don't start any agents. When it's ready, show me the files and the exact commands to start 1 lead and 3 helpers, each in its own git worktree."
Part 1: https://www.binance.com/square/post/387073609143735
3/3