bmad-market-research

$npx mdskill add bmad-code-org/BMAD-METHOD/bmad-market-research

Forwards market research requests to bmad-deep-recon.

  • Solves the need to run market research via a deprecated skill.
  • Depends on bmad-deep-recon and customization override files.
  • Resolves custom overrides then delegates to bmad-deep-recon with market type.
  • Emits a deprecation notice and forwards the request transparently.

SKILL.md

.github/skills/bmad-market-researchView on GitHub ↗
---
name: bmad-market-research
description: 'Deprecated — forwards to bmad-deep-recon (market type).'
---

# DEPRECATED — forwards to bmad-deep-recon (market type)

This skill was consolidated into `bmad-deep-recon`. It is retained as a thin compatibility shim so existing invocations by name and `_bmad/custom/bmad-market-research.toml` override files keep working. New work should invoke `bmad-deep-recon` directly — it drafts deep-research prompts for outside tools, processes finished reports into downstream-ready summaries, and runs research directly, across market, domain, technical, competitive, user-voice, and academic-lit types (plus a select shape for choose-between decisions and custom types).

## On Activation

1. Resolve customization: `uv run {project-root}/_bmad/scripts/resolve_customization.py --skill {skill-root} --key workflow`. This picks up any `{project-root}/_bmad/custom/bmad-market-research.toml` and `bmad-market-research.user.toml` overrides for the legacy fields (`activation_steps_prepend`, `activation_steps_append`, `persistent_facts`, `on_complete`).
2. Emit a deprecation notice to the user (in their configured communication language): `bmad-market-research` is deprecated and forwards to `bmad-deep-recon` with the market type. To silence this notice and access the full new surface (draft/process/run modes, research types, verification levels, HTML briefing, handoffs), migrate `_bmad/custom/bmad-market-research.toml` to `_bmad/custom/bmad-deep-recon.toml` and invoke `bmad-deep-recon` directly.
3. Invoke `bmad-deep-recon` with: **research type** `market` (skip its type inference), the four legacy fields above as pre-resolved values, and the user's original input verbatim. `bmad-deep-recon` takes the workflow from here — do not execute any further steps in this shim.

More from bmad-code-org/BMAD-METHOD

SkillDescription
bmad-advanced-elicitationPush the LLM to reconsider, refine, and improve its recent output. Use when user asks for deeper critique or mentions a known deeper critique method, e.g. socratic, first principles, pre-mortem, red team.
bmad-agent-analystStrategic business analyst and requirements expert. Use when the user asks to talk to Mary or requests the business analyst.
bmad-agent-architectSystem architect and technical design leader. Use when the user asks to talk to Winston or requests the architect.
bmad-agent-devSenior software engineer for story execution and code implementation. Use when the user asks to talk to Amelia or requests the developer agent.
bmad-agent-pmProduct manager for PRD creation and requirements discovery. Use when the user asks to talk to John or requests the product manager.
bmad-agent-tech-writerTechnical documentation specialist and knowledge curator. Use when the user asks to talk to Paige or requests the tech writer.
bmad-agent-ux-designerUX designer and UI specialist. Use when the user asks to talk to Sally or requests the UX designer.
bmad-architectureProduce the architecture: a lean spine of invariants that keeps everything built from it consistent, projected into whatever format the work needs. Use when the user says "create the architecture", "create technical architecture", "architecture spine", or "create a solution design".
bmad-brainstormingFacilitate a brainstorming session using diverse creative techniques. Use when the user says 'help me brainstorm' or 'help me ideate'.
bmad-check-implementation-readinessValidate PRD, UX, Architecture and Epics specs are complete. Use when the user says "check implementation readiness".