Isolate

Begin a managed worktree round trip: create one branch and sibling worktree with a recorded route back to its base.

Consult the lifecycle contract when recovering from failure or changing package behavior; the steps below are the execution path. isolate owns the shared runtime used by the companion integrate and discard skills.

Steps

1. Resolve the task, <repo-root>, <branch>, and <base>.

   • Resolve <repo-root> with git rev-parse --show-toplevel from the current checkout.
   • Name <branch> as type/short-kebab-description, for example feat/power-management.
   • Use the user-selected <base>, otherwise the current branch, otherwise main.
   • Rewrite the request as a compact handoff prompt containing only task intent and explicit constraints. Omit $isolate so the next session continues the task.

   This step is complete when all four values are explicit and the handoff prompt continues the task instead of invoking isolation again.

   The base worktree may be dirty: isolation starts the new branch at the base branch's committed HEAD and leaves local base changes in place.