Quick Overview
In this build demonstration, Nate Herk introduces a decision-making skill for Claude Code called the Roast Room. The video walks through how multi-agent architectures can be structured to debate business strategy using distinct advisor personas. Herk explains the underlying file system, the three-round debate logic, and how users can adapt the tool to their own workflows.
Key Points
- 1.The Roast Room is a Claude Code skill that simulates a board of seven business advisors debating a strategic question across three structured rounds.
- 2.The advisor personas include Jeff Bezos, Paul Graham, Alex Hormozi, Gary Vaynerchuk, Dan Martell, Gino Wickman, and Warren Buffett, each backed by curated markdown source files.
- 3.The system architecture relies on sub-agents communicating through a central chair rather than an unconstrained group chat, keeping token costs predictable and preventing premature consensus.
- 4.Deliberations follow three phases: individual opening stances, targeted peer cross-examination, and final voting with weighted scoring and actionable caveats.
- 5.All session transcripts, debate rounds, and final verdicts are recorded to project files and can be exported as formatted PDF reports.
- 6.Users can replace the default personas with domain-specific advisors by supplying scraped background texts, decision rules, and distinct reasoning frameworks.
Summary
Nate Herk demonstrates the Roast Room, an advisory board system running as a skill inside Claude Code. The system convenes simulated council personas representing Jeff Bezos, Paul Graham, Alex Hormozi, Gary Vaynerchuk, Dan Martell, Gino Wickman, and Warren Buffett. Each persona focuses on a distinct business lens. Bezos assesses whether a decision is reversible and a good bet, Graham evaluates genuine user demand, and Buffett analyzes cash impact, risk, and long-term value. Herk demonstrates the system by feeding it a founder dilemma regarding whether to commit to an in-person conference in Austin in June 2027 or pursue virtual alternatives.
The council deliberates across three rounds coordinated by an agent acting as the Chair. In round one, each advisor evaluates the brief independently and generates an opening position. This prevents the personas from anchoring on whoever speaks first. The advisors score options from one to ten, with the Austin demonstration showing unanimous initial support for a scaled-down in-person tier. When an option achieves universal backing, the Chair triggers an intentional counter-argument phase in round two, ordering specific personas like Buffett and Martell to push back and argue hard for alternative paths. Personas challenge one another directly using their core operational principles.
After cross-examination, round three concludes with final votes and a comprehensive verdict. For the demonstration query, the council returns an approval labeled Go with conditions, specifying that the organizer must pre-sell fifty paid memberships before signing venue contracts and establish hard refund deadlines. The skill stores all session output into markdown files, including event logs, intermediate rounds, and a final verdict document. Herk shows how this output is rendered in a custom visual web interface with avatar speech bubbles, as well as an exported PDF report complete with advice breakdowns and recommended action items.
Herk opens the project code repository to illustrate how the advisors are configured. Rather than using unstructured system prompts, each persona possesses a sub-agent definition file mapped to a knowledge directory called a brain. For example, the Hormozi persona draws from 124 public talks containing 1.3 million words, organized into files detailing eight decision rules, named frameworks, stances, and illustrative stories. The Bezos persona contains data from twenty-four shareholder letters and thirty-seven public interviews. Herk emphasizes that users can duplicate this structure to build advisors for any domain, such as technical security or executive leadership, by scraping relevant subject matter expertise into structured markdown documents.
Architecture of the Roast Room Skill
The Roast Room runs inside Claude Code as an automated advisory council moderated by an agent called the Chair. Rather than executing a free-for-all group chat where models anchor to the first statement made, the process uses independent sub-agents. Each persona writes an initial stance alone before reading what other advisors wrote. The Chair controls communication, routes disagreements, synthesizes proposals, and drives the council toward an unambiguous vote and verdict.
Constructing Advisor Brains and Knowledge Files
Each advisor persona consists of an agent configuration file and a folder of markdown documents representing their knowledge base. The configuration establishes the advisor's worldview, preferred questions, speaking style, and decision rules. Detailed supporting files store public source materials, frameworks, principles, positions, and stories compiled from transcribed interviews, shareholder letters, podcasts, and books, allowing the model to ground its advice in actual recorded history.
The Three-Round Deliberation and Scoring Process
A deliberation starts with the user submitting a decision, concrete options, numbers, deadlines, and current inclinations. In round one, each advisor scores the options from one to ten and states an opening argument. In round two, the Chair highlights friction points and directs specific advisors to debate each other. In round three, advisors cast final votes, leading to an overall verdict report that outlines next steps, safety conditions, and dissenting opinions.
Replay Interface and Session Exports
While the core skill executes in the terminal through Claude Code, a companion browser user interface visualizes the council proceedings. The interface displays animated avatars, real-time message streams, option scorecards, and clickable breakdowns of advisor arguments. Past sessions remain fully browsable in the local file system or UI, and users can export complete debate summaries as standalone PDF documents for team review.
The Bottom Line
The presentation establishes how multi-agent debate structures can yield thorough business critiques without the conversational drift typical of open group chats. It demonstrates practical implementations of grounded agent personas backed by custom corpora within Claude Code. The video leaves open how the system handles larger or contradictory unstructured enterprise datasets that have not been pre-processed into clean markdown files.
FAQ
What is the Roast Room and how does it function inside Claude Code?
The Roast Room is a multi-agent Claude Code skill that gathers seven simulated business advisors into a three-round structured debate to evaluate strategic founder questions.
Why does the Roast Room use independent sub-agents instead of a group chat?
Sub-agents write their initial responses alone, which prevents personas from anchoring to whoever speaks first, maintains predictable token costs, and ensures genuine disagreement.
What business advisors are included by default in the Roast Room council?
The council consists of Jeff Bezos, Paul Graham, Alex Hormozi, Gary Vaynerchuk, Dan Martell, Gino Wickman, and Warren Buffett.
How are the individual advisor brains constructed inside the project repository?
Each advisor has an agent configuration file connected to markdown documents containing rules, frameworks, past stories, and transcribed source material extracted from public talks, books, and interviews.
What details should a user provide when submitting a question to the council?
A user should provide a one-line decision statement, two or three clear options, financial figures, resource limits like deadlines and budget, definitions of success, and current personal leanings.
Worth watching for
Founders, operators, and developers looking to stress-test business decisions using multi-agent debate workflows in Claude Code.
- claude-code
- ai-agents
- multi-agent
- prompt-engineering
- business-strategy
- sub-agents