The trading team · Guide 04
Bull and Bear: the debate that protects you from yourself
In one lineTwo fresh chats get the same packet and argue opposite sides from evidence only, so you hear the best case against your trade before your money does.
What you'll get
- Why the debate works, and the one setup mistake that ruins it.
- The full Bull and Bear prompts, plus a one-minute rebuttal round.
- The pre-mortem: assume the trade lost, and name the three most likely reasons before you enter.
- How to read a debate: not who "won", but whether the Bear's best point was answered.
- A worked debate on the NQ example, start to finish.
1Why a debate, and not a second opinion
A second opinion from the same kind of chat, asked the same kind of question, mostly gives you the same answer. A debate is different: two roles with opposite jobs, arguing from the same evidence. The Bull must name the strongest point against itself. The Bear must say what would prove it wrong. You're not looking for a winner. You're looking for the point that matters, and whether anyone answered it.
The debate also gives you a habit most traders never build: hearing the case against a trade before taking it, every single time, including the times you're sure.
2The rule that makes it work: clean chats
The debate leans. The gate decides if you can trade at all.
Bull and Bear argue from the same packet in separate chats. The Risk Manager never sees the debate: it checks your rules and your account, and a BLOCK stands however the debate went.
- Fresh chats. The Bull runs in chat B, the Bear in chat C. Neither has seen chat A's conversation, and neither has seen you get excited.
- Same packet, word for word. Analyst brief + setup watch + one line describing the scenario. Paste the outputs, not your summary of them.
- No hints. Don't write "I like this one" or "be tough on it". The prompts already set the job.
- Round 1 is independent. Each side writes its case without seeing the other's.
- Round 2 is optional and short. Each side sees the other's case once and replies in five lines, conceding what's right. Never more than one rebuttal round. Long debates drift into word games.
3The Bull
Bull prompt (fresh chat B)
Role: Bull.
Below is today's packet: the Analyst brief, the setup watch and the scenario under review.
Make the best HONEST case for taking this scenario today.
You may not:
- Use anything that is not in the packet. No outside knowledge of this market, no "typically", no "institutions".
- Predict a price, give a percentage, or use the words "obvious", "can't lose" or "high probability".
- Praise the plan. Adjectives about quality are not evidence.
Reply in exactly this format:
BULL CASE — {setup name} — {date}
1–3. Up to 3 reasons, strongest first. Each ends with the packet section it rests on (Brief 2, Watch 1...).
What must happen next for this case to hold: one or two observable events.
The strongest point against my case: you must name one, with its packet section.
Confidence: Low, Medium or High, and one sentence why.
If the packet supports fewer than 3 reasons, give fewer. Do not pad.
If two or more context rules are CAN'T TELL, confidence cannot be High.
Before you send: check that every reason cites a packet section and that "strongest point against" is filled.
PACKET
{paste Analyst brief}
{paste setup watch}
Scenario under review: {e.g. "Long from watch zone 1 if the trigger rule prints between 09:45 and 11:00 ET"}4The Bear
Bear prompt (fresh chat C)
Role: Bear.
Below is today's packet: the Analyst brief, the setup watch and the scenario under review.
Make the strongest HONEST case against taking this scenario today.
Check, in this order:
1. Rule failures: any context rule marked FAIL or CAN'T TELL, and any no-trade condition close to being met.
2. Location: is the watch zone in the middle of a range, into a higher-timeframe level, or far from invalidation?
3. Event risk: any scheduled event or blackout window inside or near the trade window.
4. Regime mismatch: does the regime label fit the kind of setup this is?
5. The "wait" option: what would a better version of this plan look like, and what does waiting cost?
You may not:
- Use anything that is not in the packet. "The market could crash" is not a point.
- Invent a level, an event or a statistic to strengthen your case.
- Soften a point to be agreeable, or pad the list to look thorough.
Reply in exactly this format:
BEAR CASE — {setup name} — {date}
1–4. Up to 4 points, strongest first. Each ends with the packet section it rests on.
What would prove me wrong: one observable event.
Confidence: Low, Medium or High, and one sentence why.
If the packet gives you fewer than 4 honest points, give fewer. If it gives you none, write "No point against found in the packet" and list what evidence is missing that would let you check.
Before you send: check that every point cites a packet section and none is generic.
PACKET
{paste Analyst brief}
{paste setup watch}
Scenario under review: {the same line you gave the Bull}5Round 2 (optional, one minute)
Paste the Bear's case into the Bull chat and the Bull's case into the Bear chat:
Role: Bull, round 2.
Here is the Bear's case. Reply in at most 5 lines.
- Concede every point that is correct. Say "conceded".
- Answer only the points you can answer with evidence from the packet, citing the section.
- Do not introduce new reasons. Do not repeat round 1.
{paste Bear case}Role: Bear, round 2.
Here is the Bull's case. Reply in at most 5 lines.
- Concede every point that is correct. Say "conceded".
- Say which of your round-1 points still stand, and why, citing the packet section.
- Do not introduce new points. Do not repeat round 1.
{paste Bull case}6The pre-mortem: assume it lost
The debate argues about the plan. The pre-mortem starts from the other end: the trade was taken exactly as written and it was stopped out. Why?
The wording matters. "What could go wrong?" invites polite, hedged answers. "It went wrong. Explain it." gets specific ones. The technique comes from project planning (Gary Klein, "Performing a Project Premortem", Harvard Business Review, 2007) and it transfers well to a trade card.
Run it once the Trader has written the card (Guide 05), in the Bear's chat C, which already holds the packet. It takes a minute. Each reason comes with a tell: something you can see on a chart or a clock that shows the failure starting. Tells the card's cancel-if lines don't cover go into line 8 of the memo.
Pre-mortem prompt (chat C, after the trade card)
Role: Bear. Job: PRE-MORTEM.
Assume it is the end of the session. The trade card below was taken exactly as written and it was stopped out for a full loss.
Write the three most likely reasons, using only the packet above in this chat and the card.
Trade card:
{paste the trade card}
You may not:
- Use reasons that are not supported by the packet or the card. No "unexpected news", no "manipulation", no general market lore.
- Say how likely the loss is, or whether I should take the trade.
- Offer comfort, encouragement or a fix that changes the stop, target or size. If you see a flaw in the card, name it. I decide what to do.
Reply in exactly this format:
PRE-MORTEM — {setup name} — card {A/B}
1. Reason: {one sentence} · Evidence: {packet section or card line} · Tell: {one observable event during the session that would show this starting} · Covered by a cancel-if on the card? YES / NO
2. (same four parts)
3. (same four parts)
Not covered: the tells that no cancel-if on the card catches. These are mine to watch.
Out of my control: any reason that is only "the setup lost this time". Write it once, without elaborating. Losses that follow the rules are part of the plan.
If the packet supports fewer than three reasons, give fewer and say "packet supports {n}". Do not pad to three.
Before you send: check that every reason cites a packet section or card line, and that every tell is something I can see on a chart or a clock.7How to read the debate
Ignore the confidence words for a moment and answer three questions:
- What is the Bear's single best point? Usually it's about location (where the entry sits), event risk, or a rule that couldn't be checked.
- Did the Bull answer it with evidence from the packet? "It'll be fine" isn't an answer. "The event is at 14:00, outside the window (Brief 3)" is.
- If it wasn't answered, can it be? Sometimes a better screenshot or exported data turns a CAN'T TELL into a PASS or a FAIL. Sometimes the honest answer is to wait.
Those three answers go straight into the Decider's memo (Guide 05). An unanswered Bear point about event risk or location caps the score at 2.
8Worked example: the debate on the NQ plan
Illustrative. The packet is the brief and watch from Guide 03. Prices are examples.
Scenario under review: "Long from watch zone 1 (21,449–21,455) if the trigger rule prints between 09:45 and 11:00 New York."
Bull (round 1):
- Higher-timeframe structure is up on 4H and 1H, with a 1H higher low at 21,402 (Brief 1).
- All three context rules PASS with evidence (Watch 1).
- No pasted event inside the 09:30–11:00 window (Brief 3).
- What must happen next: the trigger sequence completes at the watch zone; price doesn't close a 5m candle back inside the range below 21,440.
- Strongest point against my case: the target, the prior day high at 21,492.25 (Brief 2), is only about 40 points above entry, so the reward is capped near 2R.
- Confidence: Medium. Rules pass, but volume isn't visible (Brief 6).
Bear (round 1):
- Location: entry at ~21,452 sits about 40 points below the prior day high, 21,492.25 (Brief 2). Any stall below that level cuts the trade short of 2R.
- The opening range is narrow, 20.75 points (Watch 3). Narrow ranges can produce several false breaks before a real one.
- Unknown participation: volume isn't visible (Brief 6). The trigger could print on thin activity.
- The wait option: a retest after a 1H close above 21,492 would remove the overhead level. Waiting costs nothing if the trigger doesn't print.
- What would prove me wrong: the trigger prints and price holds above 21,452 for two 5m closes.
- Confidence: Medium.
Round 2, Bull: "Concede point 1: the target is capped by the prior day high. Point 2: the trigger rule needs a return and a close back above, which filters some false breaks (Setup sheet). Point 3 stands, volume isn't visible. Point 4 is a different setup, not in my rules."
Round 2, Bear: "Concede that the trigger rule filters a single false break. Point 1 stands: the plan has about 2R of room, and nothing in the packet says the prior day high will break."
Reading it: the Bear's best point is location (2R of room under a known level). The Bull conceded it, which is honest, and it doesn't break any rule. Point 3 (volume) is unanswered. The trader adds a volume pane to tomorrow's screenshots. This goes to the Decider as: best point for, structure and rules pass; best point against, limited room under the prior day high.
Pre-mortem on the card (after Guide 05's Trader step): three reasons, each from the packet. Stalled under the prior day high (Brief 2). False break of a narrow range (Watch 3), with the tell "a 5m close back below 21,440 before the retest completes". Thin participation (Brief 6), which can't be watched without a volume pane. The second tell isn't covered by a cancel-if, so it goes into the memo's line 8.
9Common mistakes
- Running both sides in one chat. The Bear reads the Bull and softens. Separate chats are the whole point.
- Skipping the Bear when you're excited. That's exactly when it earns its keep.
- Treating it as a vote. Two Mediums don't average to anything. Read the best point.
- Arguing with the Bear yourself. If you have evidence, add it to the packet and rerun. Don't debate a chat.