The /handoff skill is so great. I use it to plan with Claude Code using /grill-me, and delegate that plan to multiple worktrees running Codex

I made an extended video about all the delegation strategies I'm using right now

This the the thrust of my workflow plugin for Claude. I made an ACP gateway, to pass through tool permissions and questions for the user.

been doing the same setup. the moment the worktrees start diverging on implementation is where you actually learn what your spec was missing.

oh nice this looks pretty useful for a lot of the ping pong I’m doing

@mattpocockuk 🤟🤟

Is this cmux?

This is the underrated pattern: use one model for adversarial planning, then hand a scoped artifact to execution agents. A lot of agent pain is really context-shape pain.

bro is running a digital clone army 😏

How many worktrees are you running in parallel before it gets hard to manage?

在claude code中使用吗？

splitting planning from execution across worktrees keeps context clean, really handy when iterating on vision stacks. curious how you handle merge conflicts when agents touch overlapping files

Would be great if GPT-5.5 would actually care about the content of a plan but it doesn't in Codex for me, not even when it's its own plan.

using /grill-me and /handoff just demonstrates the lack of understanding of your own code. do your self a favor and use to let you and your agents understand better your codebase

planning and implementation as separate workloads routed to different models — this is the multi-model pattern that actually works. curious how you handle it when a Codex worktree hits a blocker mid-task though?

the handoff file is the boundary. without owner, branch, tests, weird state, and expected proof, parallel agents just turn one vague task into four confident messes.