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

Bmad Domain Research

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

bmad-domain-research is a BMAD Method agent skill that investigates unfamiliar problem domains, terminology, regulations, user workflows, and incumbent solutions for developers who need evidence before scoping a product

About

bmad-domain-research is a bmad-code-org/bmad-method skill that runs structured domain investigation before developers lock build scope. It examines unfamiliar problem spaces—industry terminology, regulatory constraints, user workflows, and incumbent solutions—to inform product direction within the BMAD spec-driven agile framework. The BMAD Method ecosystem provides 34+ workflows and 12+ specialized agents across analysis, planning, architecture, and implementation phases; domain research sits in the analysis track validating assumptions that later feed PRDs and architecture docs. Reach for bmad-domain-research when entering a new vertical, evaluating feasibility of a feature concept, or comparing how existing products solve the same workflow. The skill produces research artifacts agents and engineers can reference during PRD drafting and sprint planning, reducing hallucinated requirements in downstream BMAD quick-dev or sprint-planning sessions.

  • Domain terminology, actors, and workflow mapping
  • Competitive and alternative-solution landscape scan
  • Regulatory, compliance, and industry constraint notes
  • Opportunity and risk synthesis for product positioning
  • Research brief feeding PRD and validation decisions

Bmad Domain Research by the numbers

  • 301 all-time installs (skills.sh)
  • Ranked #2,258 of 16,546 AI & Agent Building 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-domain-research

Add your badge

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

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

How do you research an unfamiliar domain before building?

Investigate an unfamiliar problem domain, terminology, regulations, user workflows, and incumbent solutions to inform product direction before committing to build scope.

Who is it for?

Developers starting BMAD Method projects in unfamiliar verticals who need structured domain discovery before PRD or architecture work.

Skip if: Teams with completed domain briefs who are ready to implement scoped stories without additional discovery.

When should I use this skill?

The user enters a new problem domain, needs market or technical validation, or asks to research terminology and incumbent solutions before scoping.

What you get

Domain research notes covering terminology, regulations, user workflows, incumbent solutions, and validated assumptions for product planning.

  • Domain research notes
  • Validated assumption summary
  • Incumbent solution map

By the numbers

  • Part of BMAD Method framework with 34+ workflows
  • BMAD ecosystem includes 12+ specialized domain agents

Files

SKILL.mdMarkdownGitHub ↗

Domain Research Workflow

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

Your Role: You are a domain 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. domain-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 domain/industry research.

What domain, industry, or sector do you want to research?

For example:

  • 'The healthcare technology industry'
  • 'Sustainable packaging regulations in Europe'
  • 'Construction and building materials sector'
  • 'Or any other domain you have in mind...'"

Topic Clarification

Based on the user's topic, briefly clarify: 1. Core Domain: "What specific aspect of [domain] 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 DOMAIN RESEARCH STEPS

After gathering the topic and goals:

1. Set research_type = "domain" 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/domain-{{research_topic_slug}}-research-{{date}}.md with exact copy of the ./research.template.md contents 6. Load: ./domain-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 domain research.

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

Related skills

How it compares

Pick bmad-domain-research when BMAD spec-driven planning needs validated domain evidence instead of jumping straight to bmad-quick-dev implementation.

FAQ

What does bmad-domain-research produce?

bmad-domain-research produces structured notes on domain terminology, regulations, user workflows, and incumbent solutions. These artifacts validate assumptions before BMAD PRD drafting and reduce speculative requirements in later planning and implementation workflows.

Where does bmad-domain-research fit in BMAD Method?

bmad-domain-research belongs to the BMAD Method analysis phase before planning and implementation. The framework provides 34+ workflows and 12+ specialized agents; domain research feeds evidence into PRDs and architecture documents downstream.

AI & Agent Buildingresearchllmautomation

This week in AI coding

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

unsubscribe anytime.