otto-handofflisted

# Handoff Skill Transfer the current task - context, decisions, failed attempts, constraints - to a fresh agent. The receiving agent starts with **zero context**, so the handoff prompt must be a self-contained briefing. **User's arguments:** $ARGUMENTS ## Prerequisites Read the **otto** skill. Before choosing a provider, call `list_personalities` (role `coder`); if the host has a coder personality that fits, hand off to it by name. Otherwise read `~/.otto/orchestration-preferences.json` unless the user explicitly named a provider in this request. Do not create the receiving agent until you have done one of these. ## Parsing arguments 1. **Provider or personality** - explicit user request first; otherwise a `coder` **personality** from `list_personalities` (pass its name as `create_agent`'s `personality`), or, failing that, resolve a provider from `impl` preference (or `ui` if the task is styling-only). 2. **Worktree** - "in a worktree" / "worktree" → create a worktree via Otto with a short branch name derived from the task, based on the current branch. 3. **Task description** - anything else the user said. ## The handoff prompt The receiving agent has zero context. Include: ``` ## Task [Imperative description.] ## Context [Why this task exists, required context.] ## Relevant files - `path/to/file.ts` - [what it is and why it matters] ## Current state [What's done, what works, what doesn't.] ## What was tried - [Approach] - [why it failed or was abandoned] ## Dec