paseo-advisor

# Paseo 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 **paseo** skill. Before choosing a provider, read `~/.paseo/orchestration-preferences.json` unless the user explicitly named a provider in this request. Do not create the advisor until you have read it. ## Picking the advisor 1. **User named one** (`--provider claude/opus`) → use it. 2. **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` 3. **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 only. Do NOT edit, create, or delete any files. Do NOT write code. ``` ## Forwarded skills If `$ARGUMENTS` contains another skill reference — `/unslop`, `/unslop-risk`, `$unslop`, etc. — the user is asking the advisor to run that skill against the current task. Examples: - `/paseo-advisor /unslop` → advisor runs `...