otto-advisorlisted

# Otto Advisor Single agent. Reads the situation you're in. Gives a judgment. You decide what to do - the advisor doesn't drive the work. **User's request:** $ARGUMENTS ## Prerequisites Read the **otto** skill. Before choosing a provider, call `list_personalities` (role `advisor`); if the host has an advisor personality, prefer it. Otherwise read `~/.otto/orchestration-preferences.json` unless the user explicitly named a provider in this request. Do not create the advisor until you have done one of these. ## Picking the advisor 1. **User named one** (`--provider claude/opus`) → use it. 2. **Advisor personality available** → spawn it via `create_agent`'s `personality` argument (it already carries the right provider/model/effort/prompt). This is the preferred path when the host has one. 3. **Otherwise** resolve from preferences - pick the category that matches the question: - Design / approach question → `planning` - "Did I miss something" review → `audit` - "Is this even right" → `research` 4. **Contrast helps.** If your own provider matches what preferences would pick, swap to a different family on purpose - fresh perspective is the point. ## The briefing The advisor has zero context. Make it self-contained: - The question, sharply. - What you've considered and what you've ruled out. - Relevant files by path (don't paste - let the agent read). - Explicit ask: "give me a recommendation, with reasoning." End with the no-edits suffix: ``` This is analysis onl