bmad-technical-research
Deprecated — forwards to bmad-deep-recon (technical type).
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
菜单
Deprecated — forwards to bmad-deep-recon (technical type).
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Strategic business analyst and requirements expert. Use when the user asks to talk to Mary or requests the business analyst.
Create, update, or validate a product brief. Use when the user wants help producing, editing, or validating a brief.
Deprecated — forwards to bmad-deep-recon (domain type).
Deprecated — forwards to bmad-deep-recon (market type).
Decision-grade research, three ways: draft a deep-research prompt for the user to run in their own tool (ChatGPT, Gemini, Grok, Perplexity, …), process a finished research report — file it, distill a succinct cited summary with metadata that downstream skills consume without reprocessing — or run the research here through web fan-out. Shipped type packs: market, domain, technical, competitive, user-voice, academic-lit — plus a select shape for choose-between decisions and custom types via overrides. Use when the user says "deep recon", "research this", "draft a research prompt", "process this research report", "market research", "domain research", "technical research", "competitor research", "literature review", or "help me choose between".
Create, update, or validate a PRD. Use when the user wants help producing, editing, or validating a PRD.
| name | bmad-technical-research |
| description | Deprecated — forwards to bmad-deep-recon (technical 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-technical-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-technical-research.toml and bmad-technical-research.user.toml overrides for the legacy fields (activation_steps_prepend, activation_steps_append, persistent_facts, on_complete).bmad-technical-research is deprecated and forwards to bmad-deep-recon with the technical 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-technical-research.toml to _bmad/custom/bmad-deep-recon.toml and invoke bmad-deep-recon directly.bmad-deep-recon with: research type technical (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.