Skip to content
🤖 AI-optimized docs: llms-full.txt

Discover Your Module Idea

Use this guide to discover what BMad module you should build. You’ll learn to identify problems, recognize opportunities, and validate ideas that others will also find valuable.

  • You’re interested in building a module but don’t know what to build
  • You have a vague idea but need to clarify the specifics
  • You want to ensure your module solves a real problem
  • You’re looking for ideas that could be valuable to others
  • You already have a clear, specific module concept in mind
  • You’re building a module for a well-defined team need
  • You’re following the tutorials with example ideas

The best modules solve real problems.

BMad can build modules for ANY domain — but that doesn’t mean every module idea is worth building. The most successful modules:

  1. Solve a problem you actually have — You understand the pain point deeply
  2. Leverage your unique expertise — You know what “good” looks like
  3. Apply to others too — If you need it, chances are others do as well

This guide helps you find that intersection.

Start by listing things that frustrate you. Good module ideas often come from personal annoyance.

CategoryQuestions
WorkWhat tasks do you repeat constantly? What processes feel unnecessarily complex? What do you procrastinate on?
LifeWhat do you struggle to organize? What decisions do you overthink? What do you forget to do?
LearningWhat did you have to learn the hard way? What do you wish someone had taught you?
ExpertiseWhat do you know that others find confusing? What questions do you keep answering?
FrustrationModule Concept
”I never remember what my therapist told me”Therapist Agent with session memory
”Doing my taxes is overwhelming”Tax Workflow with personalized deduction hunting
”I can’t keep track of my novel’s characters”Story Architect Module with character bibles
”I forget workout progress”Fitness Coach Module that remembers and evolves
”Legal documents are intimidating”Legal Office Module that explains and drafts

Write down everything — no idea is too small or weird.

What do you know that others might not? Your modules will be better when they draw on your deep knowledge.

TypeExamplesModule Potential
ProfessionalLawyer, doctor, accountant, teacherDomain-specific workflows and agents
HobbyCooking, gaming, gardening, musicSpecialized tools and guides
Life ExperienceParenting, relationships, relocationNavigational aids and coaching
CreativeWriting, art, photographyCreative process assistants

List 3-5 areas where you have above-average knowledge:

  1. _______________ (what problems do people face in this area?)
  2. _______________ (what mistakes do beginners make?)
  3. _______________ (what could be streamlined?)
  4. _______________ (what repetitive tasks exist?)
  5. _______________ (what’s missing from existing tools?)

The sweet spot is where your frustrations and your expertise overlap.

Low FrustrationHigh Frustration
High ExpertiseNiche Expert Tools — Help others do what you do easilyPremium Modules — Solve problems you know deeply AND hate
Low ExpertisePassion Projects — Learn while buildingAvoid — Hard to build well, unclear if valuable

Focus on High Expertise + High Frustration — these make the best modules.

Low FrustrationHigh Frustration
High ExpertiseWorkout builder (easy for them, valuable to others)Fitness Coach Module (solves their own tracking frustration + uses their expertise)
Low ExpertiseMeal planning app (fun to learn)Tax prep module (hard, not their domain)

Before committing to an idea, test it with three questions:

Too vague: “A cooking module” Just right: “A Meal Planning Module that generates weekly grocery lists based on dietary restrictions, pantry inventory, and family preferences”

Narrow your scope until you can describe what the module DOES in one sentence.

If you wouldn’t use it regularly, why would anyone else?

Be honest: Is this a “nice to have” or a “must have” for you?

You don’t need a mass market, but you need enough users to make building worthwhile.

Good signals:

  • Friends/colleagues have the same problem
  • Online communities discuss this frustration
  • Existing solutions are expensive or inadequate

Based on your idea, choose the best starting point:

If You Want To…Start With
Automate a repetitive taskAgent — Simple or Expert depending on complexity
Guide someone through a processWorkflow — Step-by-step facilitation
Share a complete solutionModule — Multiple agents + workflows
IdeaBest Starting PointWhy
”Generate better commit messages”Simple AgentFocused task, no memory needed
”Help me write my novel”Expert AgentOngoing project, needs context
”Guide me through brainstorming”WorkflowProcess-oriented, doesn’t need memory
”Complete legal office suite”ModuleMultiple components, complex system

After completing this guide, you’ll have:

  • 3-5 validated module ideas ranked by your interest and expertise
  • Clarity on the problem your module will solve
  • Confidence in market need based on your own experience
  • A starting point (agent, workflow, or full module)

You’ll be ready to move to:

Sarah’s Journey:

  1. Frustration: “I’m a therapist and I can never remember what clients told me last session”
  2. Expertise: Clinical psychology, session documentation, treatment planning
  3. Intersection: High expertise (therapist) + High frustration (session tracking)
  4. Specific Idea: “Therapist Agent that records session notes, remembers client goals, tracks progress over time”
  5. Validation:
    • Specific? Yes — session memory and progress tracking
    • Would she use it? Weekly, every session
    • Could 100 others use it? Yes, every therapist she knows
  6. Starting Point: Expert Agent (needs persistent memory for client data)

Result: Sarah builds a Therapist Agent that becomes her practice’s backbone — then publishes it to the BMad marketplace where hundreds of therapists discover and use it.

Start small. Your first module should solve ONE problem well, not ten problems poorly.

Build for yourself first. If you genuinely need and use your module, others will too.

Document everything. As you build, note what works and what doesn’t — this becomes your module’s documentation.

Iterate publicly. Share early versions with friends or communities. Feedback shapes better modules.

Think ecosystem, not competition. Your “Therapist Agent” could complement someone else’s “Clinical Notes Module.” Collaboration beats competition.

Once you have your module idea:

  1. Choose your tutorial: Agent, Workflow, or Module creation
  2. Create your module brief (for modules): Run [PB] with Morgan to formalize your vision
  3. Build incrementally: Start with the minimum viable version, then enhance based on use
  4. Share your work: Publish to npm or the upcoming BMad marketplace