Your work is held to the bar a top expert in its field sets.
Claude Code. With moo off, you say three rule branches conflict with main and ask Claude to resolve them, one subagent per branch, each in its own worktree. Claude starts three subagents and explains the conflict, and a second problem git won't flag: the rule count merges cleanly to the wrong number. As each subagent finishes, Claude checks its branch itself, then reports all three resolved in a table, and warns that they will conflict again as each lands. With moo on, you type /hope:deepen and the same words. A dialog asks how to resolve the rule count, and you pick derive it, and whether to merge or rebase, and you pick merge main in. The reply sets the bar a release engineer would: start from each branch's merge-tree, replace the hardcoded count with a test, and pass on green tests and no conflict. One gap stays open: the others clash again once one lands. It proposes starting the three subagents.