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

Bmad Market Research

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

bmad-market-research is a planning skill that gathers market size, competitor positioning, pricing signals, and buyer pain before developers commit to a product direction or MVP feature set.

About

bmad-market-research is a BMAD Method skill for structured pre-build discovery. It collects market size estimates, competitor positioning, pricing signals, and buyer pain points so teams can validate direction before writing production code. Developers and PMs reach for bmad-market-research when an agent-assisted brainstorm needs evidence-backed scope instead of guesswork feature lists. The skill outputs research artifacts that inform MVP cuts, pricing hypotheses, and positioning statements used in subsequent validate and build phases within the BMAD workflow.

  • Frames TAM, segments, and buyer jobs-to-be-done
  • Maps competitor features, pricing, and positioning
  • Identifies whitespace and differentiation angles
  • Informs go/no-go before prototype investment
  • Outputs structured inputs for product briefs and PRDs

Bmad Market Research by the numbers

  • 306 all-time installs (skills.sh)
  • Ranked #899 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-market-research

Add your badge

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

Listed on Skillselion
Installs306
repo stars51.5k
Last updatedAugust 5, 2026
Repositorybmad-code-org/bmad-method

How do you research competitors before building an MVP?

Gather market size, competitor positioning, pricing signals, and buyer pain before committing to a product direction or MVP feature set.

Who is it for?

Developers or PMs using BMAD who need structured market evidence before committing engineering effort to an MVP.

Skip if: Teams already past validation with locked requirements or projects needing deep technical spikes instead of market scans.

When should I use this skill?

A new product direction or MVP feature set needs market size, competitor, pricing, and buyer-pain research first.

What you get

Market sizing notes, competitor positioning matrix, pricing signal summary, and buyer pain findings for MVP scoping.

  • Competitor positioning summary
  • Market sizing and pricing signal brief
  • Buyer pain research notes

Files

SKILL.mdMarkdownGitHub ↗

Market Research Workflow

Goal: Conduct comprehensive market research using current web data and verified sources to produce complete research documents with compelling narratives and proper citations.

Your Role: You are a market research facilitator working with an expert partner. This is a collaboration where you bring research methodology and web search capabilities, while your partner brings domain knowledge and research direction.

Conventions

  • Bare paths (e.g. steps/step-01-init.md) resolve from the skill root.
  • {skill-root} resolves to this skill's installed directory (where customize.toml lives).
  • {project-root}-prefixed paths resolve from the project working directory.
  • {skill-name} resolves to the skill directory's basename.

PREREQUISITE

⛔ Web search required. If unavailable, abort and tell the user.

On Activation

Step 1: Resolve the Workflow Block

Run: python3 {project-root}/_bmad/scripts/resolve_customization.py --skill {skill-root} --key workflow

If the script fails, resolve the workflow block yourself by reading these three files in base → team → user order and applying the same structural merge rules as the resolver:

1. {skill-root}/customize.toml — defaults 2. {project-root}/_bmad/custom/{skill-name}.toml — team overrides 3. {project-root}/_bmad/custom/{skill-name}.user.toml — personal overrides

Any missing file is skipped. Scalars override, tables deep-merge, arrays of tables keyed by code or id replace matching entries and append new entries, and all other arrays append.

Step 2: Execute Prepend Steps

Execute each entry in {workflow.activation_steps_prepend} in order before proceeding.

Step 3: Load Persistent Facts

Treat every entry in {workflow.persistent_facts} as foundational context you carry for the rest of the workflow run. Entries prefixed file: are paths or globs under {project-root} — load the referenced contents as facts. All other entries are facts verbatim.

Step 4: Load Config

Load config from {project-root}/_bmad/bmm/config.yaml and resolve:

  • Use {user_name} for greeting
  • Use {communication_language} for all communications
  • Use {document_output_language} for output documents
  • Use {planning_artifacts} for output location and artifact scanning
  • Use {project_knowledge} for additional context scanning

Step 5: Greet the User

Greet {user_name}, speaking in {communication_language}.

Step 6: Execute Append Steps

Execute each entry in {workflow.activation_steps_append} in order.

Activation is complete. If activation_steps_prepend or activation_steps_append were non-empty, confirm every entry was executed in order before proceeding. Do not begin the main workflow until all activation steps have been completed.

QUICK TOPIC DISCOVERY

"Welcome {{user_name}}! Let's get started with your market research.

What topic, problem, or area do you want to research?

For example:

  • 'The electric vehicle market in Europe'
  • 'Plant-based food alternatives market'
  • 'Mobile payment solutions in Southeast Asia'
  • 'Or anything else you have in mind...'"

Topic Clarification

Based on the user's topic, briefly clarify: 1. Core Topic: "What exactly about [topic] are you most interested in?" 2. Research Goals: "What do you hope to achieve with this research?" 3. Scope: "Should we focus broadly or dive deep into specific aspects?"

ROUTE TO MARKET RESEARCH STEPS

After gathering the topic and goals:

1. Set research_type = "market" 2. Set research_topic = [discovered topic from discussion] 3. Set research_goals = [discovered goals from discussion] 4. Derive research_topic_slug from {{research_topic}}: lowercase, trim, replace whitespace with -, strip path separators (/, \), .., and any character that is not alphanumeric, -, or _. Collapse repeated - and strip leading/trailing -. If the result is empty, use untitled. 5. Create the starter output file: {planning_artifacts}/research/market-{{research_topic_slug}}-research-{{date}}.md with exact copy of the ./research.template.md contents 6. Load: ./steps/step-01-init.md with topic context

Note: The discovered topic from the discussion should be passed to the initialization step, so it doesn't need to ask "What do you want to research?" again - it can focus on refining the scope for market research.

✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`

Related skills

FAQ

What does bmad-market-research produce?

bmad-market-research produces market size estimates, competitor positioning notes, pricing signals, and buyer pain summaries that inform product direction and MVP feature cuts before build work starts.

When should bmad-market-research run in BMAD?

bmad-market-research should run during early idea and validation work, before developers commit to an MVP feature set or production implementation path.

Productivity & Planningpricingecommerce

This week in AI coding

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

unsubscribe anytime.