$npx -y skills add aj-geddes/claude-code-bmad-skills --skill bmad-researchConducts market, competitive, domain, and technical research using live web sources, producing a cited research-report.md to inform BMAD planning decisions. Use when the user says: - "research [topic/market/technology]" - "competitive analysis" or "who are the competitors" - "mar
| 1 | # BMAD Research |
| 2 | |
| 3 | Conducts structured, cited research across three modes to feed BMAD planning workflows. |
| 4 | Output is a research-report.md in bmad-output/, ready for handoff to planning skills. |
| 5 | |
| 6 | --- |
| 7 | |
| 8 | ## Step 0 — Clarify Intent |
| 9 | |
| 10 | Before searching, confirm: |
| 11 | |
| 12 | 1. **Mode** — Create / Update / Validate (default: Create) |
| 13 | 2. **Research type** — Market | Competitive | Technical | Domain (may combine) |
| 14 | 3. **Topic** — What is being researched? |
| 15 | 4. **Output destination** — Default: `bmad-output/research-report.md` |
| 16 | |
| 17 | If project-context.md exists, read it first (`bmad-output/project-context.md`) for |
| 18 | scope constraints. |
| 19 | |
| 20 | --- |
| 21 | |
| 22 | ## Step 1 — Plan the Research |
| 23 | |
| 24 | Use the source-type strategy guide to pick sources by research type: |
| 25 | |
| 26 | ``` |
| 27 | ${CLAUDE_PLUGIN_ROOT}/skills/bmad-research/scripts/research-sources.sh |
| 28 | ``` |
| 29 | |
| 30 | Run it (Bash) to print the guide, then sketch a query plan: |
| 31 | - 3–5 targeted WebSearch queries per research type |
| 32 | - Specific URLs to WebFetch (industry reports, competitor sites, docs) |
| 33 | - Triangulation goal: each key claim backed by 2+ independent sources |
| 34 | |
| 35 | Track progress with TodoWrite. |
| 36 | |
| 37 | --- |
| 38 | |
| 39 | ## Step 2 — Execute Research |
| 40 | |
| 41 | ### Market Research |
| 42 | - Search: market size, TAM/SAM/SOM, growth CAGR, key trends, growth drivers |
| 43 | - Sources: Statista, Grand View Research, CB Insights, SEC filings, industry reports |
| 44 | - Quantify everything possible: dollar values, percentages, time frames |
| 45 | |
| 46 | ### Competitive Research |
| 47 | - Search: top competitors, feature comparisons, pricing, user reviews, funding |
| 48 | - Sources: G2/Capterra (reviews), Crunchbase (funding/size), company IR pages, |
| 49 | product documentation, Reddit/HN community sentiment |
| 50 | - Build a feature comparison matrix |
| 51 | |
| 52 | ### Technical Research |
| 53 | - Search: framework benchmarks, adoption rates, community health, known trade-offs |
| 54 | - Sources: Official docs, GitHub stars/issues, npm/PyPI stats, State of JS/CSS, |
| 55 | ThoughtWorks Radar, Stack Overflow surveys |
| 56 | - Evaluate: maturity, ecosystem, licensing, long-term viability |
| 57 | |
| 58 | ### Domain Research |
| 59 | - Search: regulatory landscape, industry standards, key players, domain glossary |
| 60 | - Sources: Government databases, standards bodies, academic papers (Google Scholar, |
| 61 | arXiv), trade publications |
| 62 | |
| 63 | **Citation discipline**: for every factual claim, record source URL + access date. |
| 64 | When a claim cannot be verified across 2+ sources, mark it `[UNVERIFIED]`. |
| 65 | |
| 66 | --- |
| 67 | |
| 68 | ## Step 3 — Update Mode |
| 69 | |
| 70 | If mode is Update, read the existing report first. Then: |
| 71 | 1. Identify sections with stale data (>6 months old, or marked `[UNVERIFIED]`) |
| 72 | 2. Re-run targeted searches for those sections only |
| 73 | 3. Append a "Last Updated" entry per section |
| 74 | 4. Increment the report version |
| 75 | |
| 76 | --- |
| 77 | |
| 78 | ## Step 4 — Validate Mode |
| 79 | |
| 80 | If mode is Validate: |
| 81 | 1. Extract all quantitative claims from the existing report |
| 82 | 2. Spot-check each claim with a fresh WebSearch |
| 83 | 3. Mark each claim: `[VERIFIED]`, `[CONTRADICTED source: …]`, or `[UNVERIFIED]` |
| 84 | 4. Append a "Validation Summary" section noting overall confidence |
| 85 | |
| 86 | --- |
| 87 | |
| 88 | ## Step 5 — Write the Report |
| 89 | |
| 90 | Use the template: |
| 91 | |
| 92 | ``` |
| 93 | ${CLAUDE_PLUGIN_ROOT}/skills/bmad-research/templates/research-report.template.md |
| 94 | ``` |
| 95 | |
| 96 | Fill all sections. Sections irrelevant to the research type may be omitted (mark as |
| 97 | N/A). Write the completed report to: |
| 98 | |
| 99 | ``` |
| 100 | bmad-output/research-report.md # or a user-specified path |
| 101 | ``` |
| 102 | |
| 103 | **Required sections regardless of mode:** |
| 104 | - Executive Summary with key findings and bottom line |
| 105 | - Research Scope (in/out of scope, time frame) |
| 106 | - Methodology (sources used, tools, limitations) |
| 107 | - Gaps & Opportunities |
| 108 | - Recommendations (planning actions, not implementation actions) |
| 109 | - Full source bibliography (Appendix B) with URLs and access dates |
| 110 | |
| 111 | --- |
| 112 | |
| 113 | ## Step 6 — Handoff |
| 114 | |
| 115 | After writing the report, tell the user: |
| 116 | - The output path |
| 117 | - The 3 most important findings in plain language |
| 118 | - Which BMAD planning skill should consume this report next: |
| 119 | - Market/Competitive → business-analyst or product-manager |
| 120 | - Technical → system-architect |
| 121 | - Domain → business-analyst |
| 122 | |
| 123 | Record the research decision in `bmad-out |