Route any request

What you'll get

The right specialist team working your problem, without you choosing one. Routing takes seconds. The work after it takes as long as the work deserves. Everything here assumes chapter 3 is done, so you are installed and onboarded.

The steps

1. Type the request.

/marg:route Our churn ticked up last month. Find out why and what to do about it.

Plain chat works once Marg is installed, but the command form guarantees routing and keeps your intent unambiguous, so reach for it when the request matters.

2. Let Marg set up before it works. In the background it checks which tools are reachable, loads your profile, classifies the request, and picks the team. You see the routing decision land, and you never have to make it.

3. Answer the clarifying question if one comes. A thin request earns one sharp question back instead of a thin answer, and that exchange is the system protecting the quality of what you get, not stalling.

4. Read the report. Findings first, then the evidence grade, then the next moves. If a move needs your approval, Marg asks before acting, because it never spends money or changes an outside system on its own. Chapter 26 covers those gates.

Requests that route well

The sharper your request, the sharper the routing and the fewer questions come back, so spend a sentence on specifics. Give the number that worries you, the constraint you are under, and the deadline if there is one. The difference is easy to see:

/marg:route Help us grow revenue.

/marg:route We are at 40k MRR, flat for 3 months. We can spend 2k a month on experiments. What do we try first?

The first request forces Marg to ask who you are before it can help. The second routes straight to the right team, anchors on real numbers, and comes back with a plan instead of a questionnaire.

Variations

• Explore before committing. Add "explore options" to the request and Marg lays out 2 to 3 routing options with confidence scores before it proceeds. This earns its keep when a request could sit with either of two teams.
• Share context without routing. /marg:btw we just hired a head of sales files the update to your profile without spawning a team or running anything. Use it for revenue, headcount, and priority changes you want remembered but not acted on.

If something goes wrong

• The wrong team picked it up: say so plainly ("this is a pricing question, not a marketing one") and Marg reroutes without starting over.
• You expected live data but got MEDIUM: the tool it needed is not connected or was unreachable, so the report shipped from what you described. Chapter 24 covers connecting it.
• Nothing happens on /marg:route: the plugin is not installed or Claude Code needs a restart, and chapter 3 has the fix.