vspawn-tree

# /vspawn-tree The user **explicitly invoked `/vspawn-tree` (Claude) or `$vspawn-tree` (Codex)** to request spawning a **standalone child session** under the current **vlx-term** session, passing the task in as its first message. The only difference from `/vspawn`: it **opens a dedicated git worktree for the child session** (a separate workspace/branch), suited to cases where you don't want to pollute the current workspace and want the child task to run on an isolated branch. > ⚠️ This is **not** an in-process sub-agent, and **not** a background Task: it is a real, visible, interactive, > resumable session tab in the vlx-term left-panel tree, run by its own process, leaving the current session > undisturbed. User input: $ARGUMENTS ## Planning and execution mode When the user requests planning and execution, add `--plan-execute`. Keep this conversation as the initiator; a new planner performs planning and review, then dispatches to persistent execution sessions. Add `--split-tasks` when the user requests task decomposition. Do not plan, split or implement the task in this conversation, and do not use in-process subagents. For a skill invocation with both flags, **automatically add `--yes`** unless the user explicitly requests the initial configuration dialog. The planner starts without a launch dialog, but its proposed tasks still require the user's final review before any executor starts. Never confirm tasks for the user. Without splitting, retain the ordinary confirma...