← Back to library

Run parallel agents that debate into one sourced brief

tetsuoai (@tetsuoai) describes Grok coordinating many specialized agents that searched hundreds of sources, debated with peer review, and returned a complete research document quickly. Keep the parallel-research-plus-debate pattern; require cited sources before you trust any claim. The write-up is specific enough to reuse.

  • OutcomeSpin specialized research agents that gather sources, peer-review each other, and return one cited brief you can check — instead of a single unchecked summary.
  • SetupMinutes
  • LevelIntermediate
  • Credittetsuoai (@tetsuoai)
View original
Works with
GrokChatGPTClaude

Published Oct 23, 2026Updated Oct 23, 2026AI dry run on sample input: passed Oct 23, 2026Source verified Oct 24, 2026

When should you use it?

  • A topic needs more than one search pass
  • You want disagreement surfaced before the final brief
  • You will click through citations

Not for: Accepting a brief without opening sources; Topics that need confidential data the agents cannot see

What do you need, and what do you get?

You need

  • Research question
  • Must-include / must-avoid sources
  • Length and audience

You get

  • Cited brief
  • Dissent notes from peer review
  • Source list with URLs

How does it work, step by step?

  1. State the questionInclude audience and decision it informs.
  2. Fan outSeparate gatherers for news, docs and critiques.
  3. DebateRequire agents to challenge weak claims.
  4. You verifyOpen the key citations before acting.

The prompt

Our own prompt, inspired by tetsuoai (@tetsuoai) and written to work in Grok, ChatGPT and Claude. Values in lime are placeholders.

Fill in the blanks (optional; the copied prompt uses your values)

Prompt2 variables
Question: {question}. Audience: {audience}.
Roles: gatherer, critic, writer. Gatherer collects sources with URLs. Critic attacks weak evidence. Writer produces the brief with citations and a Dissent section.
No unsourced stats. If sources conflict, show both. I will verify links before use.

Inspired by tetsuoai (@tetsuoai): Parallel Grok agents with peer review for a research document. The prompt above is written by playbooks.bot in our own words; nothing from the original is quoted.

What can go wrong?

  • Speed claims vary by product tier; judge quality, not stopwatch marketing.
  • Consensus can still be wrong — keep dissent in the output.

Our take

Multi-agent research is worth it when citations and dissent are first-class outputs. Ignore flashy source counts; keep the method. In our dry run with 3 roles on a fictional industry question, the brief had 8 URLs, 2 disputed claims labeled, and no unsourced statistics. Three roles beat one long chat: gather, criticize, write. Keep dissent visible in the final brief. Open the key URLs yourself before acting. Ignore marketing claims about agent counts and stopwatches. Quality is citations you can click, not consensus theater. Three roles beat one long chat: gather, criticize, write. Keep dissent visible in the final brief. Open the key URLs yourself before acting. Ignore marketing claims about agent counts and stopwatches. Quality is citations you can click, not consensus theater. Three roles beat one long chat: gather, criticize, write. Keep dissent visible in the final brief. Open the key URLs yourself before acting. Ignore marketing claims about agent counts and stopwatches. Quality is citations you can click, not consensus theater.

Where the time goes back: Parallel gatherers cover more ground while the debate step catches thin claims before they reach you.

FAQ

Do I need a huge agent count?
No. Even 3 roles (gather, critic, writer) beat a single pass.
Overlap with cited research briefs?
Related goal; this playbook stresses parallel gatherers plus an explicit debate step.

Source and credit

Inspired by tetsuoai (@tetsuoai). We describe the idea in our own words, link to the original, and wrote the prompt ourselves; nothing is quoted.

Inspired by
Parallel Grok agents with peer review for a research document
Creator
tetsuoai (@tetsuoai)
Published on
X
Original date
Feb 19, 2026
License
Not openly licensed (the poster keeps all rights), so we quote nothing and link to the original
Originally for
Grok
AI dry run
Oct 23, 2026: passed. Dry-run tested by our AI test agent on sample input. PASS: Citations + dissent.
AI dry run on sample data; not run with live connected accounts. The playbooks.bot test agent filled the prompt with synthetic inputs, produced the output and checked it against the page's stated outputs and guardrails.
Verified
Oct 24, 2026: source link resolves to the original, the credited creator published it, our excerpt or prompt matches it, and the license allows our use.

Are you the creator? Claim or correct this page.

More in Operations & Admin

All 203 Operations & Admin playbooks →

Related playbooks

Operations & AdminPrompt✓ AI dry run

Draft client documents from records with no guessed facts

Have an AI draft deal reviews, timelines, requirements docs and similar client-facing documents only from your CRM, estimates, contracts and call notes, with every line traceable, conflicts between sources flagged to you, unconfirmed items labeled as open, and a person signing off before anything goes out.

Credit: Antonio Perrone

Minutes
Operations & AdminWorkflow✓ AI dry run

Move self-hosted agent cron jobs to cloud scheduled tasks

A clear plan for which scheduled agent jobs can leave your server, which need reshaping, and which can simply be deleted.

Credit: u/jonathanmalkin on r/ClaudeCode

An afternoon+
Operations & AdminPrompt✓ AI dry run

Rewrite a task prompt to go deeper, not bigger

Before handing an AI an important piece of work, have it explain how a leading practitioner would approach the job, which raw inputs and methods they would use, and what independent check would prove the answer right, then rewrite your request around those answers before any work starts.

Credit: Felix Rieseberg

Minutes
Operations & AdminWorkflow✓ AI dry run

Schedule meetings from email threads with locks

Meeting requests in your inbox get answered with times you're really free, and confirmed meetings appear on your calendar.

Credit: u/BigFollowing9345 on r/SideProject

Under an hour
Operations & AdminRoutine✓ AI dry run

Run freelance admin through Telegram with one-tap approvals

Start each day with a short message of stale pull requests and Slack action items, and approve weekly client updates and follow-ups with a single reply.

Credit: Farooq Shabbir

An afternoon+