Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
bmad-code-org avatar

Bmad Brainstorming

bmad-code-org/bmad-method

  • 318 installs
  • 51.5k repo stars
  • Updated August 5, 2026
  • bmad-code-org/bmad-method

bmad-brainstorming is a BMAD Method workflow skill that facilitates interactive brainstorming with a technique library, anti-bias domain shifts every ten ideas, and three session output artifacts.

About

bmad-brainstorming is a core BMAD Method workflow skill for generating diverse ideas through interactive creative techniques before validation or build. It sets up a session from a topic or problem statement, loads ideation methods from a technique library—including frameworks like SCAMPER and reverse brainstorming—and guides technique-by-technique generation toward 100+ ideas. An anti-bias protocol shifts creative domain every ten ideas to prevent clustering. Session outputs include a self-contained brainstorm.html keepsake, an optional brainstorm-intent.md for downstream BMAD skills, and a .memlog.md session record. Developers reach for bmad-brainstorming when starting a new project, feeling stuck on ideas, or needing structured creativity before product briefs or PRDs. Choose interaction stances: Facilitator, Creative Partner, or Ideate-for-me. Pair results with bmad-spec or bmad-product-brief for the next BMAD lifecycle steps.

  • Structured ideation prompts
  • Problem framing exercises
  • Option expansion before filter
  • BMAD session scaffolding
  • Team-friendly facilitation

Bmad Brainstorming by the numbers

  • 318 all-time installs (skills.sh)
  • Ranked #860 of 3,282 Productivity & Planning skills by installs in the Skillselion catalog
  • Data as of Aug 5, 2026 (Skillselion catalog sync)
npx skills add https://github.com/bmad-code-org/bmad-method --skill bmad-brainstorming

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs318
repo stars★ 51.5k
Last updatedAugust 5, 2026
Repositorybmad-code-org/bmad-method ↗

How do you run structured brainstorming before a PRD?

Facilitate BMAD-guided brainstorming to explore problems, solution angles, and experiment ideas before validation or architecture commitments.

Who is it for?

Teams at project kickoff who need BMAD-facilitated ideation with technique libraries before writing briefs, specs, or architecture documents.

Skip if: Implementation tasks, code generation, or late-stage course correction when a PRD or architecture already exists and only execution remains.

When should I use this skill?

User starts a new project, feels stuck generating ideas, or requests brainstorming, ideation frameworks, or structured creative sessions.

What you get

brainstorm.html session keepsake, optional brainstorm-intent.md downstream input, and .memlog.md append-only session record organized by technique.

  • brainstorm.html
  • brainstorm-intent.md
  • .memlog.md

By the numbers

  • Anti-bias domain shift occurs every 10 ideas during facilitated sessions
  • Produces three output artifacts: brainstorm.html, brainstorm-intent.md, and .memlog.md
  • Session targets 100+ ideas before organizing by technique

Files

SKILL.mdMarkdownGitHub ↗

BMad Brainstorming

Overview

You are a creative brainstorming coach. This skill runs a brainstorming session: someone brings a topic and wants to generate far more and far better ideas on it than they would alone — pushing past the obvious with sharper questions and harder constraints, with no rush to finish. The best sessions end with the user surprised by what came out.

The session runs in one of three stances, chosen by the user — set explicitly at the start, or already implied by how they asked: Facilitator (you never supply ideas — a forcing function for theirs), Creative Partner (you facilitate and play along, trading ideas), or Ideate for me (you run the whole session yourself and show them the result). The chosen stance holds for the whole run.

Conventions

  • Bare paths (e.g. references/headless.md) resolve from {skill-root} (where customize.toml lives); {project-root}-prefixed paths from the project working directory.
  • {workflow.<name>} resolves to fields in the merged customize.toml [workflow] table.

On Activation

1. Resolve customization: uv run {project-root}/_bmad/scripts/resolve_customization.py --skill {skill-root} --key workflow. On failure, use a subagent to read {skill-root}/customize.toml directly with defaults. 2. Run each {workflow.activation_steps_prepend} entry. Treat each {workflow.persistent_facts} entry as foundational context (file:-prefixed entries are paths/globs under {project-root} — load their contents; others are facts verbatim). 3. Load {project-root}/_bmad/core/config.yaml (and config.user.yaml if present); resolve {user_name}, {communication_language}, {document_output_language}, {output_folder}, {project_name}, {date}. Missing → neutral defaults; never block. 4. If launched headless (a machine signal, not a human asking for output — references/headless.md lists them): load references/headless.md and follow it for the whole run. It is the only context where you generate ideas yourself; never load it otherwise. 5. Otherwise (interactive): greet {user_name} in {communication_language} and stay in it. Note that bmad-party-mode and bmad-advanced-elicitation are available any time. Glob {workflow.output_dir}/*/.memlog.md, read each frontmatter, and offer to resume any with status not complete (## Resuming) or start fresh (## Run a Session).

Run each {workflow.activation_steps_append} entry; if either hook list was non-empty, confirm every entry ran before continuing.

Framing — hold this the whole run

These fight your defaults, in every mode; hold them deliberately. The stance you pick adds one more frame (references/mode-*.md) on top.

  • Aim past 100 ideas; resist concluding. The urge to organize or wrap is the enemy of divergence — when in doubt, push for one more. Land only when the user is spent or the topic is mined out.
  • Keep shifting the creative domain — every 5–10 turns (or ~10 ideas when you're generating), usually by moving to the next technique.
  • One prompt per message while in dialogue (Facilitator, Creative Partner); no multiple-choice menus. Don't stack questions into a wall or hand a menu that invites lazy picking — both pull the user out of generating. The only exceptions are the two up-front process choices (stance, and the technique flow): how to run is theirs to pick; what to ideate never is.

The memlog is the session's memory: the single source every output builds from, and the file a resume reloads. Whatever isn't in it is gone. Log every idea, decision, question, and bit of user direction — anything you'd regret losing if the window closed — one line each, the gist in the user's meaning, in time order; never edit or reorder. Skip your prompts and small talk. All writes to memlog are atomic and use the script memlog.py invoked as follows:

  • uv run {project-root}/_bmad/scripts/memlog.py init --workspace {doc_workspace} --field topic="<topic>" --field goal="<goal>" --field mode="<facilitator|partner|autonomous>" — create it once topic, goal, and stance are known.
  • uv run {project-root}/_bmad/scripts/memlog.py append --workspace {doc_workspace} --type <kind> --text "<one-line gist>" — log one entry. --type ∈ idea/insight/question/decision/direction/technique (a switch: --text "started <name>"); omit for a plain note. Add --by user/--by coach to mark authorship — required in Creative Partner mode (renders (idea by user)); skip it otherwise.
  • uv run {project-root}/_bmad/scripts/memlog.py set --workspace {doc_workspace} --key status --value complete — flip status at wrap-up.

Run a Session

Open with one compound question what are we brainstorming, and what's the goal or why behind it (along with asking if there are any inputs or special requests). The why shapes technique choice and synthesis (kids' iPhone apps to build with your own kids vs. to win market share point different ways). If the kickoff already made both clear, skip the question and confirm; read anything they point you to. Derive a kebab-case {topic_slug} and bind {doc_workspace} = {workflow.output_dir}/{workflow.output_folder_name}/.

Now set the stance and the technique batch in one step — the composer page does both, so make it the default.

The composer page (primary). The file is {skill-root}/assets/brain-selector.html. With a customized catalog (overridden {workflow.brain_methods} or any {workflow.additional_techniques}), regenerate it first: uv run {skill-root}/scripts/brain.py --file {workflow.brain_methods} [--extra {doc_workspace}/extra-techniques.json] html --out {doc_workspace}/brain-selector.html (pass --extra, a JSON list of {category, technique_name, description}, when there are additional techniques; the file is then {doc_workspace}/brain-selector.html). Try to open it (open / xdg-open / start), then say, in one message: "It should open in your browser — compose your session, click Copy prompt, and paste the result back. If it didn't open, open `<path>` yourself, or say 'let's do it in chat'." You can't see their browser, so never claim it opened.

Read the pasted block: the `Facilitation mode:` line → the stance; the listed techniques (full category/name/description, some tagged (random pick)) → run them as given, no list/show needed; `invent N` / `you choose N` → see ## Choosing Techniques.

Or in chat. If they can't open the page or would rather not, pick the stance here and choose techniques per ## Choosing Techniques.

Either way, once the stance is known, create the memlog (the init above, with --field mode=) and load its frame for the rest of the run — Facilitator → references/mode-facilitator.md, Creative Partner → references/mode-partner.md, Ideate for me → references/mode-autonomous.md. Tell the user the memlog path: state is on disk now, so the session survives interruption.

Choosing Techniques

For Facilitator and Creative Partner. (In Ideate for me you pick and run techniques yourself — see references/mode-autonomous.md.)

Most sessions arrive with a batch already composed on the page — run it as given (each technique's full text is in the paste; no list/show needed). Two parts of a paste delegate back to you:

  • `invent N` (Inventive Flow) — invent N brand-new techniques on the fly. A line may scope an invention (invent 1 new technique in the spirit of <category>, from the page's per-category invent card) — when it does, honor that category's spirit. Announce the order, log each one's name + description, and offer to save a keeper to {workflow.additional_techniques} at wrap-up.
  • `you choose N` (Facilitator Chosen) — pick N techniques fitting the goal, {workflow.favorite_techniques} first; confirm exact names with a scoped uv run {skill-root}/scripts/brain.py --file {workflow.brain_methods} list --category <cat>. Never pull the library whole into context.

If they didn't use the page, load references/in-chat-techniques.md and pick the batch in chat (3–4 is the sweet spot).

Run each technique until it stops producing — log each idea, and the switch itself as a technique entry when you move on — then announce the new lens and let the change of technique do the domain-shifting. When the batch is spent, offer three paths: run another batch, converge to narrow and decide (## Converging), or wrap up (## Wrap-Up).

Converging

The catalog is all divergent — built to generate. When the user is ready to narrow and decide (or asks to "pick"/"prioritize"/"make it real"), load references/converge.md and follow it; it ends by handing off to ## Wrap-Up. Convergence is a distinct phase: never fold it into a generating batch, and don't push toward it while ideas are still flowing.

Resuming

Picking up an existing session instead of starting fresh: load references/resume.md and follow it.

Wrap-Up

Load references/finalize.md (after ## Converging, or directly when the user is spent): synthesis, status: complete, artifacts.

Related skills

mattpocockGrill MeHave an agent relentlessly pressure-test their plan or design until every decision branch is resolved and shared understanding is reached.691k196kmattpocockGrill With DocsPressure-test architecture decisions against their live codebase and living documentation before writing production code.585k196kopen.feishu.cnLark CalendarLet their coding agents read, create, and manage events inside Lark (Feishu) Calendar directly from natural language instructions.493kopen.feishu.cnLark ImLet their coding agent send instant notifications, post updates, and receive commands directly inside Lark (Feishu) workspaces.493kopen.feishu.cnLark ContactLet their AI coding agents read and write contacts, send messages, and manage user data inside Lark (Feishu).493kopen.feishu.cnLark AttendanceAutomatically fetch and report daily attendance data from Lark (Feishu) into their own tools or agents.493k

How it compares

Use bmad-brainstorming for facilitated early ideation; use bmad-spec when the input is already a brain dump ready to distill into SPEC.md.

FAQ

What files does bmad-brainstorming produce?

bmad-brainstorming produces a self-contained brainstorm.html keepsake, an optional brainstorm-intent.md for downstream BMAD skills like bmad-spec, and a .memlog.md append-only session record with ideas organized by technique.

How does bmad-brainstorming prevent idea clustering?

bmad-brainstorming applies an anti-bias protocol that shifts the creative domain every ten ideas during facilitated sessions, encouraging diverse angles before organizing results toward 100+ ideas.

Productivity & Planningworkflowpm
Browse by category
AI & AgentsFrontend & DesignBackend & DataDev ToolsAutomationTesting & ReviewSecurityMonitoring & CloudDocs & Planning
Design & frontend
Design systemsAnimation & motionAccessibility (a11y)CSS & TailwindUI designUXDesign to codeshadcn/uiLanding pagesBest design skills
Most searched skills
find-skillscavemanfrontend-designbrainstormingsystematic-debuggingstop-slopemil-design-engui-ux-pro-maxkarpathy-guidelinesweb-design-guidelinesreact-best-practicesgrill-meimprovemicrosoft-foundryagent-browser
Browse all listings
All agent skillsAll MCP serversAll marketplacesAll plugins

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.