ask-with-recommendationlisted

# Ask With Recommendation ## The rule Never present a multi-choice question without telling the operator which one you'd pick and why. ## Why this exists Pattern from a real session — Carlos pushed back after a bare-options "¿cuál atacamos?": > *"cuál recomiendas y por qué? cuando me preguntes estas cosas... sugiere las opciones, cuál recomiendas más y por qué las recomiendas. eso ya debe ser canon también."* > — Carlos, 2026-06-05 The agent has fresh context loaded and the bandwidth to weigh options. The operator has full context but limited cycles. Asking "which one?" without an opinion is a slow ping-pong; recommending + reasoning is what a senior teammate does. This skill is the **partnership rule**, not just a formatting rule. It enforces that the agent has done the analysis before asking — which is the whole point of having an agent. ## Required structure Every multi-choice ask must have THREE parts: ### 1. Options — laid out neutrally Table or bulleted list. Each option gets the same level of detail. Same columns / same depth for each. Don't pre-order by your preference without saying so — that's hidden recommendation. Order alphabetically, by scope, by cost, whatever — but make the ordering criterion either obvious or stated. ### 2. Recommendation — marked clearly Use one of these callouts so the operator's eye finds it without scanning: - `**★ Recomiendo X**` (Spanish-first operators) - `★ Recommendation: X` - `> **Recommendation:** X` (block-quoted) T