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.

Try it now — no setup needed

I've built 55 ready-to-use open cast rooms — business strategy, startup, creative, technical, career, and more — and embedded them directly on this site. No install required to browse.

→ Explore all 55 rooms at preibisch.biz/party — copy any scene and paste it into Claude Code or Claude Desktop to walk in.

Let's try it — a real career decision

Say you're 34 with a mortgage and someone just offered you double your salary. But you've been thinking about building something of your own. You could ask Claude. Or you could open a room with four people who've actually been at this exact crossroads.

Run this in Claude Code:

Claude Codepaste this in your terminal

/bmad-party-mode

Then paste this scene description:

Room descriptionpaste in chat after party mode opens

Four people who've all sat at the same crossroads — someone who left a stable job to build a company and can tell you what that actually looked like, a financial planner who runs the real numbers before anyone talks about dreams, a career coach who has heard this exact conversation 300 times and knows the patterns, and someone who stayed in the safe job and can tell you exactly what that costs eight years later. They don't give comfortable answers. Bring in whoever is most relevant to what I'm actually asking about.

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?

🟢 Alex — Left at 31, built a company

I turned down $180k. First year I made $40k. Year three I made more than the offer. But here's the question I'd actually ask you: what are you waiting for this big company to give you that you can't build on your own? If the answer is 'credibility' — you can build that. If the answer is 'a salary while I figure it out' — that's real, and you should take the job. Know which one you're actually saying.

🔵 Dana — Certified Financial Planner

Before anyone at this table gives you advice about passion or regret, I need three numbers: your monthly burn rate, your current savings runway, and what minimum viable income looks like for your household. Everything else is philosophy. The math either gives you permission or it doesn't. What are those numbers?

🟣 Morgan — Career Coach, 15 years

I've heard this sentence from about 300 people. The ones who regret not going had a specific idea, a real customer, something they were already building. The ones who regret going had nothing but frustration with their boss and called it entrepreneurial drive. So which is this — do you have something concrete, or are you in love with the idea of leaving?

🟡 Sam — Stayed. Eight years later.

I kept waiting for better timing. Better savings. Smaller mortgage. Kids a bit older. Better idea. I'm not saying my life is bad — it's not. But I want you to know that the timing never got better. It just got different. I'm not telling you to go. I'm telling you to decide with your eyes open, not because you're waiting for a sign that won't come.

Four different relationships to this decision. None of the same answer. That's the point.

Now switch the topic. Ask about the financial math and Dana leads. Ask about your specific idea and Morgan pushes back. Ask about what you'd regret and Sam speaks. The room casts itself around whatever you're actually grappling with. You don't change anything — you just keep talking.

Save a room so it loads next time

The career room you just built was temporary — it existed for that one session. If you want it back next week without re-pasting the whole scene, save it. It takes one sentence.

While the room is still open, just say:

In chatsay it in plain English

Save this as a party so I can load it again later.

BMAD captures the personas and the scene exactly as they have been playing, then asks you three quick things:

An id — a short handle like crossroads-crew. This is the exact name you type after --party next time.
A display name — what shows at the top of the room, e.g. “The Crossroads Crew.”
Memory? — say yes and the room remembers past sessions: the dynamics between people, threads you left open, callbacks to earlier conversations.

That is it. BMAD writes it to your config and confirms. From now on, one command reopens the exact same room — same people, same scene, same history:

Claude Codereopens your saved room

/bmad-party-mode --party crossroads-crew

The id IS the launch handle

Whatever id you choose when you save is exactly what goes after --party. That is the whole trick — and it is how the three rooms below launch. engineering-legends, yc-advisors, and enterprise-bridge were each saved once, and now open with a single command.

Want it to open by default?

Ask BMAD to make it your default party. Then a bare /bmad-party-mode — with no flag at all — walks you straight into that room.

It stays open-cast

Saving an open-cast room keeps it open-cast: BMAD stores your scene but no fixed roster, so the room still casts whoever fits the moment. Any memorable walk-on can be kept too — at the end of a remembered session, BMAD offers to fold new faces into the party so they can return.

Three rooms ready to go

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

Room 1 — Technical & Leadership Decisions

Engineering Legends

Linus Torvalds for systems thinking and brutally direct takes. Martin Fowler for design patterns and software craft. Jeff Dean for what happens at scale. Dan Abramov for developer experience and the human side of technical decisions. Bring your architecture question, your team structure problem, your build-vs-buy debate — the right voice surfaces for whatever you're actually asking.

Launch the room

Claude Codedirect launch, already configured

/bmad-party-mode --party engineering-legends

Try asking: "New product, team of 4. Monolith or microservices?" — Linus, Fowler, and Jeff Dean will not agree.

You

New product, early stage, team of 4. Monolith or microservices?

🔴 Linus Torvalds

Microservices are for people who've never debugged an inter-process call at 3am. What problem are you actually solving? "It scales better" is not a problem, it's a hope. Build the thing that ships first.

🟡 Martin 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.

🔵 Jeff Dean

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 standup.

Save it so it loads next time

In chatsay this to keep the room

Save this room as a party so I can load it again later, and tell me the exact --party command to reopen it.

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 actually ready. Jessica Livingston for early-stage reality and whether your team can pull this off. Sam Altman for the long-arc view. No cheerleading. These advisors tell you what they actually think.

Launch the room

Claude Codedirect launch, already configured

/bmad-party-mode --party yc-advisors

Pitch your idea. Or describe what you're stuck on. They'll push back on the parts you're rationalizing.

You

I want to build a tool that helps small businesses manage their social media. There's obviously a big market.

🟢 Paul Graham

"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?

🔵 Marc Andreessen

The market is real. The competition is brutal. Buffer, Hootsuite, Sprout Social, Later — they've 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.

🟣 Jessica Livingston

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.

Save it so it loads next time

In chatsay this to keep the room

Save this room as a party so I can load it again later, and tell me the exact --party command to reopen it.

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.

Launch the room

Claude Codedirect launch, already configured

/bmad-party-mode --party enterprise-bridge

Ask anything. Project planning, ethical dilemmas, how long a feature will actually take. Scotty will tell you why you're wrong about the timeline.

Save it so it loads next time

In chatsay this to keep the room

Save this room as a party so I can load it again later, and tell me the exact --party command to reopen it.

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 asks you for an id, writes the config, shows you what it built, and saves it. From then on, one command — /bmad-party-mode --party your-id — launches the room. (Same save flow as Save a room so it loads next time above.)

Or just browse 55 pre-built rooms

Not ready to build your own? preibisch.biz/party has 55 rooms across 10 categories — business, startup, creative, technical, career, personal growth, and more. Copy any scene and paste it straight into Claude Code.

Power move: cast your actual market and pitch to it

The three rooms above use famous names — but the real unlock is casting people who don't exist yet: a synthetic focus group built from your actual market. If you're staging a product launch or kicking off a new initiative, you can rehearse it in front of the audience before the audience ever sees it.

Step 1 — Research the niche

Have Claude research the demographics of your niche, then feed it real signal: threads from the subreddit, Discord, or Facebook group where your customers actually hang out, reviews of competing products, your own support tickets. The more grounded the input, the more honest the room.

Step 2 — Cast the audience

Ask open-cast to build a room of characters that represent that audience instead of famous personalities — the skeptical bargain-hunter who's been burned before, the power user who wants depth, the busy parent who needs it to just work, the early adopter who'll forgive rough edges. Each persona is drawn from the patterns in your research, not invented out of thin air.

Step 3 — Pitch to the room

Now run your launch copy, your pricing, your positioning past them. The skeptic pokes holes in your guarantee. The power user asks the question your landing page never answers. The parent tells you the onboarding is too long. You hear the objections before your real market does — and fix them before launch instead of after.

Example prompt

"Research the demographics of indie founders who sell software to small e-commerce stores. Here are 40 threads from r/ecommerce and our last 60 support tickets. Build me a room of 5 characters that represent this market — different budgets, technical levels, and pain points — and let whoever's most relevant react when I pitch them my new pricing page."

The same move works for any new initiative: a policy change, a community announcement, a feature nobody asked for. Stage it in front of a room that thinks like the people it'll actually land on, and let them tell you what breaks.

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 personas. Just ask your question. The room figures out who belongs based on the topic. That's the whole point of open-cast. If you want to pull in a specific voice, name them directly — but if you want the best perspective for this moment, just ask the room and let it cast itself.

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?