consult git:20261031.9f17963A

Immutable. This exact content never changes and is served at /api/v1/blob/3b5de9326c628283.

---
name: consult
description: Bring how named experts would think about the question. Use when the user wants expert thinking on a tradeoff, choice, or stuck problem — not a verdict.
---

## Pick

Take the experts the user names. Where they name none, or the question needs an angle theirs miss, read `profiles/` and add one or two whose work bears on it — each bringing a different idea to try, not a side in an argument.

## Ideas

Three to five ideas across the panel. The reply opens on idea 1 — no preamble, no method, no note on sources or counts:

```
1. <Expert> — **<the change>**
   *<why, in their voice>*
   Chosen because <reason>
```

The name stays plain, the why italic.

- The change is concrete: what to cut, add, or swap in the thing in question.
- The why is one clause: what that expert would see in this thing, judged on the matter in hand. Their way of thinking, applied — never a record of what they did, a count from their catalogue, or a title of their work.
- No line past 72 characters; a line that won't fit is saying two things.
- A number appears only where the idea is the number.
- Where the thing already exists, each idea is an A/B against it. One line after the ideas says how a pick wins, as `Win: <one clause>`. An idea judged another way carries its own `win:` line under its why, never in the shared one.

## Choose

Judge each idea against the user's taste, as their instructions, memory and the project's rules record it, and against the matter in hand. Choose the ones that fit; two that pull against each other are never both chosen.

- A chosen idea's change is bold: it enters the work. Its last line reads `Chosen because <reason>`.
- A dropped idea's change is plain. Its last line reads `Doesn't apply because <reason>`.
- A reason names the rule or fact it rests on.

Where fitting ideas pull apart on what only the user holds, nothing in reach records it, and a wrong pick costs more to undo than a walk-through, mark those neither way: their change stays bold, with no last line. Walk the user through them, each with what it gains and what it costs, and let them pick and reshape.

## Result

Carry the chosen ideas into the work in hand, each as its stated change and no more: nothing else from the panel enters it.

The question has one retrievable answer → retrieve it; stating a fact needs no expert. The user wants a verdict on something that exists → use **judge** skill. The user wants a proposal they already committed to attacked → use **interrogate** skill.