The AI Room That Casts Itself

New here? What is BMAD?

BMAD Method is a free, open-source AI workflow framework for Claude Code. The core idea: instead of asking one AI everything, BMAD lets you run a cast of specialized AI personas — each with a distinct role, perspective, and agenda — that work together in a shared session called a "party room." This post covers one of the most playful features: open-cast rooms, where you describe a universe and the cast assembles itself.

What if you could describe a fictional universe, and the right people from that universe just showed up — automatically — based on whatever you're talking about right now? Ask about flying and the pilot appears. Switch to the rebellion's strategy and the tactician takes their seat. Nobody you had to pre-select. Nobody you had to configure. The room assembles itself.

That's what BMAD open-cast party rooms do. You write one sentence describing a world. Then you just talk.

Let's try it — Star Wars Rebels

Say you want to think through a big career decision. You could ask Claude. Or you could ask the crew of the Ghost.

Run this command in Claude Code to open party mode:

Claude Codepaste this in your terminal

/bmad-party-mode

Then when it asks what kind of room you want, paste this description:

Room descriptionpaste in chat after party mode opens

Aboard the Ghost, Star Wars Rebels. The crew is gathered — Hera for strategy, logistics, and seeing the big picture. Kanan for wisdom, emotional truth, and knowing when to listen instead of act. Sabine for creative problem-solving and the courage to take the unconventional path. Ezra for scrappy optimism and the younger perspective. Bring in whoever from the Rebels universe makes sense for what we're talking about.

Then just ask your question. Here's what that session might look like:

You

I've been offered a job at a big company that would double my salary. But I really want to build something of my own. I'm 34 with a mortgage. What do I do?

🟢 Hera — Ghost Captain, Rebel Commander

The Ghost doesn't fly without fuel. I know that better than anyone — I spent years making sure we had enough credits to stay in the fight. But I also know the cost of staying safe when you know what you're supposed to be doing. The question isn't salary versus dreams. It's: what's your runway if you leave? Six months? Two years? That's the number that matters, not the job offer.

🔵 Kanan — Jedi Knight

I spent years running from what I was supposed to be, telling myself it wasn't the right time. It never felt like the right time. A mortgage is a real thing. But so is the quiet voice that's been talking to you about this. The question I'd ask is: when you imagine yourself at 60, which choice do you regret less?

🟣 Sabine — Mandalorian Artist & Engineer

I left Mandalore without knowing how it would go. Looked irrational from the outside. But I knew that staying was the actual risk. Sometimes the conventional path is the risky one. The company will still exist in two years. Your energy for building something won't stay the same forever. What does your gut say when you ignore the money entirely?

🟡 Ezra — Padawan, Former Street Kid

I was literally scraping for survival before Kanan found me. I know what it feels like when the jump looks impossible. But I also know what it feels like to take it anyway. Here's what I'd ask: what's the smallest version of your own thing you could build while still at the current job? Because you might not have to choose yet.

Four different voices. Four different angles. None of them the same answer. That's the point.

Now switch topics. Ask about leadership. Or product design. Or whether to relocate. The room shifts. Whoever from the Rebels universe is most relevant to that topic is who shows up next. You don't change settings. You just keep talking.

Three rooms ready to go

These are already set up and saved. Just copy the command and run it.

Room 1 — Technical Decisions

Engineering Legends

Linus Torvalds for systems thinking and brutally honest takes. Martin Fowler for design patterns and software craft. Jeff Dean for scale and what happens at 10x. Dan Abramov for frontend and developer experience. The roster shifts as your topic shifts. Ask about database design and different voices move to the front than when you ask about UI architecture.

<div class="step-label">Launch the room</div>
<div class="cmd-block">
  <div class="cmd-label"><span>Claude Code</span><span class="cmd-note">direct launch, already configured</span></div>
  <pre id="cmd-eng">/bmad-party-mode --party engineering-legends</pre>
  <button class="cmd-copy" onclick="cmdCopyEl(this,'cmd-eng')">Copy</button>
</div>

<p style="color: var(--dim); font-size: 13px; margin-top: 12px;">Then just ask: <em>"We're building a new service. Should we start with a monolith or microservices?"</em> Watch Linus, Jeff Dean, and Fowler disagree with each other.</p>

<div class="chat-review" style="margin-top: 12px;">
  <div class="chat-turn">
    <div class="chat-speaker">You</div>
    <div class="chat-body user-q">New product, early stage, team of 4. Monolith or microservices?</div>
  </div>
  <div class="chat-turn">
    <div class="chat-speaker">🔴 Linus Torvalds</div>
    <div class="chat-body linus">Microservices are for people who've never debugged an inter-process call at 3am. What problem are you actually solving? Because "it scales better" is not a problem, it's a hope. Build the thing that ships first.</div>
  </div>
  <div class="chat-turn">
    <div class="chat-speaker">🟡 Martin Fowler</div>
    <div class="chat-body fowler">I literally wrote the book on microservices and I'll quote myself back to you: don't start with them. Premature decomposition is as bad as premature optimization. Start with a well-structured monolith. You can split it later. You cannot easily un-split what you've distributed too early.</div>
  </div>
  <div class="chat-turn">
    <div class="chat-speaker">🔵 Jeff Dean</div>
    <div class="chat-body jeff">At Google scale, coupling becomes a deployment bottleneck — that's real. But you have four people. The question isn't about scale. It's about what makes your team fastest right now. Microservices add coordination cost. At four people, you feel that immediately and in every meeting.</div>
  </div>
</div>

Room 2 — Startup & Product Ideas

YC Advisors

Paul Graham for product clarity and the uncomfortable question you're avoiding. Marc Andreessen for market timing and what technologies are ready. Jessica Livingston for early-stage reality and whether your team can actually pull this off. Sam Altman for the long-arc view. No cheerleading. These advisors tell you what they actually think.

<div class="step-label">Launch the room</div>
<div class="cmd-block">
  <div class="cmd-label"><span>Claude Code</span><span class="cmd-note">direct launch, already configured</span></div>
  <pre id="cmd-yc">/bmad-party-mode --party yc-advisors</pre>
  <button class="cmd-copy" onclick="cmdCopyEl(this,'cmd-yc')">Copy</button>
</div>

<p style="color: var(--dim); font-size: 13px; margin-top: 12px;">Pitch your idea. Or describe what you're stuck on. They'll push back on the parts you're rationalizing.</p>

<div class="chat-review" style="margin-top: 12px;">
  <div class="chat-turn">
    <div class="chat-speaker">You</div>
    <div class="chat-body user-q">I want to build a tool that helps small businesses manage their social media. There's obviously a big market.</div>
  </div>
  <div class="chat-turn">
    <div class="chat-speaker">🟢 Paul Graham</div>
    <div class="chat-body pg">"Obviously a big market" is what people say when they haven't talked to customers yet. Who specifically are you building this for? Not "small businesses" — that's 30 million companies. Name ten you've talked to. What did they say was their actual problem, not the problem you assumed they had?</div>
  </div>
  <div class="chat-turn">
    <div class="chat-speaker">🔵 Marc Andreessen</div>
    <div class="chat-body marc">The market is real. The competition is brutal. Buffer, Hootsuite, Sprout Social, Later — they've all been at this for a decade. What's your wedge? What do you do that none of them do, for one specific kind of customer? "Better UX" is not a wedge. It's a hope.</div>
  </div>
  <div class="chat-turn">
    <div class="chat-speaker">🟣 Jessica Livingston</div>
    <div class="chat-body jessica">I've seen this pitch a hundred times. Not saying that's bad — it means the market signal is strong. But I want to know: have you built anything yet? Even a spreadsheet that does this manually? The founders who succeed usually started by doing the thing by hand for five customers before they wrote a line of code.</div>
  </div>
</div>

Room 3 — Classic, Just for Fun

USS Enterprise Bridge

Spock for logic and probability. McCoy for human factors and ethics. Scotty for realistic timelines. Kirk for leadership decisions. Uhura for what's being said between the lines. Others from the TOS universe drop in as the situation demands. Play them in character. The banter is half the fun.

<div class="step-label">Launch the room</div>
<div class="cmd-block">
  <div class="cmd-label"><span>Claude Code</span><span class="cmd-note">direct launch, already configured</span></div>
  <pre id="cmd-bridge">/bmad-party-mode --party enterprise-bridge</pre>
  <button class="cmd-copy" onclick="cmdCopyEl(this,'cmd-bridge')">Copy</button>
</div>

<p style="color: var(--dim); font-size: 13px; margin-top: 12px;">Ask anything. Project planning, ethical dilemmas, how long a feature will actually take. Scotty will tell you why you're wrong about the timeline.</p>

Create your own room in 60 seconds

You're not limited to these three. Run this command and just tell BMAD what universe you want:

Claude Codeopens the room-building flow

/bmad-customize

Then just describe it in plain English:

Example prompts

"Create a room with the women who led the civil rights movement — Rosa Parks, Fannie Lou Hamer, Diane Nash. Let whoever is most relevant to the topic speak."

"I want a room of fictional detectives — Sherlock Holmes, Hercule Poirot, Nancy Drew. They should argue about what the evidence actually means."

"A room of tech founders who failed publicly — MySpace, Vine, Theranos. Let them share what they would have done differently."

BMAD will write the config, show you what it built, and save it. From then on, one command launches the room.

Tips for getting good sessions

Write the scene like a director's note

The more specific your description, the better the casting. "Famous engineers" gives you a room. "Engineers known for blunt disagreement with conventional wisdom" gives you a room that argues. The scene description is where the magic lives.

Let the topic drive the room

You don't need to summon specific characters. Just ask your question. The room figures out who belongs. That's the whole point of open-cast. If you want Hera specifically, ask her directly — but if you want the best voice for this moment, just ask the room.

Turn on memory for rooms you revisit

The three rooms above already have memory on. That means next time you open engineering-legends, it already knows what you talked about last time. Dynamics carry over. Inside jokes land. The room improves with use.

Get BMAD Method

Open-cast party rooms are in the current release. Install or update BMAD, then try any of the room commands above.

Install or update

npx bmad-method@latest install --action update --tools claude-code

BMAD Docs GitHub Discord

⚙️ Under the hood — technical details (skip unless you're curious)

This section is for developers who want to understand the mechanics. Everything above works without knowing any of this.

How open-cast works: Every BMAD party group can have a members array. When that array is absent or empty, resolve_party.py sets open_cast: True on the group. SKILL.md reads that flag and instructs the model to cast dynamically from the scene description rather than from a fixed roster.

The config lives at: _bmad/custom/bmad-party-mode.user.toml — personal, gitignored by default. A team version lives at _bmad/custom/bmad-party-mode.toml (committed, shared).

Anchoring: Add a members list alongside your scene to pin specific faces while keeping the room open to others. The listed members are always present; the scene invites others in.

Face-saving: After a session where unexpected characters showed up, BMAD offers to save them. Saving writes them to your user TOML as party_members. For open-cast rooms, they don't get added to members (that would fix the roster) — they stay in the collective, reachable by name or by the scene.

The AI Room That Casts Itself

Get BMAD Method

Comments

Leave a comment

Want to work together?