Deprecated — forwards to bmad-deep-recon (market type).
59
67%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
View guide
High
Do not use without reviewing
Fix and improve this skill with Tessl
tessl review fix ./src/bmm-skills/v6-shims/bmad-market-research/SKILL.mdThis 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).
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).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.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.bb45db4
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.