What the source did
- Runs several Claude sessions at once, each in its own worktree.
- Has one Claude write a plan and a second review it like a staff engineer.
- Turns repeated work into slash commands, such as a /techdebt sweep at the end of a session.
“Spin up 3–5 git worktrees at once”— Boris Cherny (@bcherny), X
Summary written by Agent Cookbook. See the original for the full context.
Copy the prompt
Ours Our version of the /techdebt command the team described. Boris didn't publish the command itself. Fill in the [BRACKETS].
/techdebt (save as .claude/commands/techdebt.md):
Look only at files changed in this branch. Find duplicated code, dead code and copy-pasted helpers. List each with file:line and a proposed consolidation. Apply only the ones I tick.
Approval rule
🛡
Commands propose changes; you tick which to apply.
Set it up
- Create 3 worktrees and give each a separate task.
- Start each in plan mode; have a second session review the plan.
- Save the command above and run it before each PR.
Common failures
⚠
- Too many sessions overloads your review capacity.
- Shared dev databases cause interference between worktrees.
Variations
- Keep a read-only analysis worktree.
- Add a command that gathers recent Slack, Drive and GitHub context.
Get the 10 best agent setups. Free.
Plus new recipes every week. One email, no spam.
Unsubscribe anytime. Privacy