spawn-sessionlisted

# Spawn a Task in a Separate Session Hand a task prompt to a new agterm session running its own `claude` or `codex` process — a visible terminal session the user can switch to and drive, which keeps running after this conversation ends. Not an `Agent` subagent: those are in-process, hidden, and die with this conversation. ## Step 1: Resolve the task prompt - Use `$0` if given. - Otherwise write a self-contained prompt: what to do, which files/areas are involved, how to verify it's done. The new session cannot see this conversation. ## Step 2: Name and workspace - Session name: short sidebar label, e.g. `Spawn: <slug>`. - One of several slices of a larger job: pick one short workspace name and reuse it verbatim for every slice, which groups them in the sidebar. Otherwise omit it — the session opens in the current workspace. - Slices sharing a stateful resource (database, lock, port): spawn one at a time, not back to back. ## Step 3: Choose a runtime Ask with `AskUserQuestion` — question "Which CLI should the new session run?", header "Runtime", single-select, options: - **Claude** (Recommended) — a `claude` process, matching this session - **Codex** — a `codex` process (Codex CLI) ## Step 4: Choose a model Check the Step 3 answer before asking — do not default to the Claude tier list out of habit just because it's the familiar one from other planning skills. Codex gets its own, different question. **If Claude was chosen**, ask with `AskUserQuestion` — ques