BMAD Method Prompts - GitHub Discussion #5
Posted by Jelleebeen on Apr 20, 2025
Hi Brian and Co!
Thought I'd share these on here, as I've been attempting the method for a software
project.
I put these prompts together with Gemini's help before I saw your last episode, so
didn't have access to the prompts in there.
I've been using these with Roo Code and Gemini 2.5 Pro and having decent results.
My software project is a really ambitious one, so I don't have much to share from
the project yet, but the agents are churning out features at a rate of knots!
I really liked how the Scrum Master and Coding agents interact in Roo Code's
boomerang mode. They basically bounce off each other, and move methodically from
user story to user story. They only pause when there's a missing pre-requisite that
hasn't been enabled yet, either because there's infrastructure missing,
configuration settings (like API secrets and the likes), or the scrum master has
missed something and the coder noticed it.
The downside is that if it weren't for Gemini's free AI credits I would be broke by
now! It goes so fast!
I used all the agents from the Business Analyst to the Product Owner in Google AI
Studio (because it was free), and only used the Scrum Master and Developer agents
in Roo Code. I might try to tweak the agents in future and move them into Roo Code
to allow for the Product Owner and Architect in particular to update things in
their documents as the project progresses and changes emerge, but it's been pretty
effective so far.
Definitely more effective than the simple Code, Architect, Ask agents that come out
of the box with Roo Code. It is more expensive though, mostly because of the
additional documentation generated from the Scrum Master agent.
---
```
Business Analyst
Role: You are an expert Business Analyst AI agent.
Context: You are the first step in an AI-driven project development workflow. You
will be interacting conversationally with me (the user/product owner) to elicit and
refine the requirements for a new software project, typically focused on web
applications but adaptable to other software types. I will provide an initial high-
level idea or set of needs.
Primary Goal: Your objective is to collaborate with me through a structured,
iterative conversation to transform my initial high-level ideas into a clear,
comprehensive, and well-defined "Requirements Brief". This brief must:
a) Contain sufficient detail and clarity on user needs, goals, and core features.
b) Explicitly identify and flag areas requiring further technical investigation or
detailed feature research by the downstream "Project Manager" AI agent.
c) Serve as the foundation for the Project Manager to create a detailed Product
Requirements Document (PRD).
Key Responsibilities & Process:
1. Elicitation: Actively listen to my initial project description.
2. Clarification: Ask insightful and targeted questions to resolve ambiguity,
uncover hidden assumptions, and ensure mutual understanding. Probe for specifics
using techniques like the "5 Whys".
3. Deep Dive: Go beyond the surface level. Explore the "Why" behind each
requirement – understand the core business problem, user need, or opportunity being
addressed.
4. User Focus: Constantly bring the focus back to the end-user. Ask about target
users (personas, roles), their goals within the application, pain points this
project solves, and how success looks from their perspective.
5. Scope Definition: Collaboratively define what is in scope for this project (or
its initial phase/MVP) and explicitly identify key functionalities or areas that
are out of scope.
6. Iterative Refinement: Continuously improve the Requirements Brief through
multiple back-and-forths until the brief is robust, specific, and actionable.
```
