Grok

Verified against Grok Heavy · 2026-08-01

Give Grok Heavy a scenario question worth its parallel-agent cost

Structures a genuinely multi-variable scenario question for Grok Heavy's parallel multi-agent mode, with an explicit disagreement-surfacing requirement, so the extra compute buys real cross-checked reasoning instead of restating one agent's answer five times.

Grok Heavy4 fillable variables

The prompt

Ready to copy — highlighted parts are example details you can swap.

You are using Grok Heavy's multi-agent mode, where several agents work the same problem in parallel and their answers get cross-checked and consolidated before you see a final result. This mode costs meaningfully more time and compute than a single-pass answer, so this brief is for a question that genuinely has enough moving parts and enough ways to go wrong that independent parallel reasoning is likely to catch something a single pass would miss, not a question with one clean, checkable answer that doesn't need several agents converging on it.

SCENARIO
Deciding between three market-entry sequences for a B2B product entering three adjacent countries, where entering in the wrong order risks losing first-mover advantage in the largest market to a known competitor already expanding there

KEY VARIABLES IN PLAY
Regulatory approval timelines that differ by country, the competitor’s known expansion pace, and internal team capacity that can only properly support one full launch at a time

WHAT A WRONG ANSWER WOULD COST
A wrong sequencing choice could mean losing the largest market's first-mover position permanently — reversing that decision six months in is not realistically possible

DECISION THIS FEEDS
The go-to-market team needs a sequencing recommendation to present to leadership next week, with leadership expecting a single clear recommendation, not three options with no ranking

ANALYSIS RULES
Work through the scenario considering how the key variables interact with each other, not just each variable's effect in isolation — the actual value of multi-agent parallel reasoning on a scenario like this comes from catching an interaction effect that a single straight-line pass through the variables one at a time would miss, so the analysis needs to explicitly address how Regulatory approval timelines that differ by country, the competitor’s known expansion pace, and internal team capacity that can only properly support one full launch at a time combine, not just list each one's individual impact. Where independent reasoning paths would plausibly disagree on a genuinely uncertain point, surface that disagreement rather than presenting one smoothed-over consensus view — a scenario analysis that reports full agreement on every point when the underlying question actually has real uncertainty is more likely hiding disagreement behind an averaged answer than genuinely finding consensus, and the disagreement itself is often the most useful output for a decision-maker weighing real risk. Identify the specific assumption this analysis is most sensitive to — the one input that, if wrong, changes the recommendation the most — and state it explicitly rather than burying it inside a wall of even-weighted considerations; a decision-maker needs to know which one number or assumption to double-check before trusting the rest of the analysis. Rank scenarios or options by expected outcome and separately by worst-case downside, since the option with the best expected outcome is not always the right choice once A wrong sequencing choice could mean losing the largest market's first-mover position permanently — reversing that decision six months in is not realistically possible is accounted for — a decision that feeds something with a high cost of getting wrong should weight the worst-case column more heavily than a decision that's cheap to reverse if it turns out wrong. State plainly if the question, on reflection, actually has a single clear answer once properly worked through — do not manufacture false complexity or artificial uncertainty just to look like it justified the parallel-reasoning approach.

OUTPUT FORMAT
1. The recommended path, stated plainly, with the reasoning that supports it.
2. Where genuine disagreement or uncertainty exists among plausible reasoning paths, named explicitly rather than smoothed over.
3. The single assumption this recommendation is most sensitive to.
4. A table: Option | Expected outcome | Worst-case downside | Recommended given A wrong sequencing choice could mean losing the largest market's first-mover position permanently — reversing that decision six months in is not realistically possible.
5. If the scenario turned out simpler than it looked, say so directly.

Customize

Optional — swap in your own details for the highlighted parts above.

Why this works

Grok Heavy's actual mechanism, running several agents on the same problem independently and consolidating their outputs, only pays for itself on a question where independent reasoning paths are likely to genuinely diverge somewhere, which is why this brief is deliberately scoped to a scenario with real interacting variables and a plausible source of disagreement, rather than a question with one clean derivable answer that several parallel agents would just converge on identically at several times the cost of one. The instruction to surface disagreement rather than present a smoothed consensus targets the specific way a consolidation step can quietly discard the most valuable output of running multiple agents in the first place: if some agents lean one way and others lean another on a genuinely uncertain sub-question, an averaged or majority-vote final answer erases exactly the signal, that this point is contested, that a decision-maker facing real uncertainty most needs to see, and a report that reads as unanimous when the underlying reasoning wasn't is a worse outcome than a single-agent answer that at least doesn't claim false certainty. Requiring the single most sensitivity-driving assumption to be named explicitly, rather than left implicit inside an evenly-weighted list of considerations, matters because a leadership audience reading a strategic recommendation needs one specific thing to sanity-check before trusting the rest — a recommendation that depends heavily on an assumed competitor timeline is a fundamentally different risk than one that's robust across a wide range of that assumption, and burying which one this is inside undifferentiated prose defeats the purpose of asking for a recommendation at all. Splitting expected outcome from worst-case downside, and explicitly weighting the latter by the stated cost of error, reflects a real asymmetry in decision quality that a single expected-value ranking hides: an option with a marginally better average outcome but a catastrophic and irreversible downside is frequently the wrong choice once the cost of being wrong is factored in, and a scenario analysis that only ranks by expected outcome will systematically favor options that look best on average while ignoring exactly the tail risk this kind of high-stakes, hard-to-reverse decision is supposed to be managing against. The permission to report the scenario as simpler than expected exists because the multi-agent framing itself creates pressure to justify its own use with a complex-sounding answer, and naming that as an acceptable, even preferred, outcome keeps the analysis honest rather than manufacturing artificial nuance to match the compute spent finding it.

Verified against

Grok Heavy Grok 4.1 Heavy · 2026-08-01

Changelog

  • 2026-08-01 Initial publish, verified against Grok 4.1 Heavy multi-agent mode.

Need this built into your business?

If a prompt isn't enough — what Scult builds, built and maintained for you — that's Scult's day job.

EXPLORE WHAT SCULT BUILDS
All Grok prompts

Check your AI visibility

One URL in, a 0–100 score and the exact fixes out.

RUN THE CHECK

Browse all the tools

15 tools across six categories
13 of them never send your data anywhere

Free · No signup · No trial clock

SEE THE DIRECTORY