market-research
Market Research — Orchestrator
Strategy — Entry point. Maps market landscape, competitors, and identifies gaps and opportunities.
Core Question: "What does the market look like, and where are the gaps worth filling?"
Critical Gates — Read First
- Markets move fast — any source older than 18 months must be flagged as historical context. Do not present stale data as current intelligence.
- TAM/SAM/SOM without methodology is a guess, not research. Every sizing estimate needs a stated method (top-down, bottom-up, or both), source, and confidence level.
- Adjacent competitors are the highest threat — do NOT skip the adjacent check. The biggest competitive threat often comes from an adjacent category expanding into yours, not from a direct competitor.
- Do NOT rely on training data for market positions or pricing — use WebSearch. Competitor data changes constantly. Always verify with live research.
Philosophy
Research rigor scales with stakes. A weekend project needs a quick landscape scan; a Series A pivot needs deep competitive intelligence. This skill produces evidence, not opinions. Every claim cites a source. Every opportunity has supporting data.
Correctness > Verifiability > Completeness > Style.
More from hungv47/strategy-skills
funnel-planner
Models business funnels with numeric targets — works backward from revenue goals to required traffic, conversion rates, and unit economics. Produces `.agents/targets.md`. Not for mapping activities to existing KPIs (use attribution) or testing specific variants (use experiment). For designing experiments to test targets, see experiment. For campaign planning, see imc-plan.
11solution-design
Brainstorms and prioritizes strategic solutions when the problem or goal is already clear — generates options, scores trade-offs, and recommends a path forward. Produces `.agents/solution-design.md`. Not for diagnosing what the problem is (use problem-analysis) or engineering task lists (use task-breakdown). For setting numeric targets after prioritizing, see funnel-planner. For technical architecture of chosen initiatives, see system-architecture.
11problem-analysis
Structured diagnosis of business and strategic problems — builds logic trees, forms testable hypotheses, and identifies root causes with evidence. Produces `.agents/problem-analysis.md`. Not for code bugs (use code-cleanup) or brainstorming solutions to a known problem (use solution-design).
10experiment
Designs validation experiments for business ideas — defines hypotheses, success metrics, sample sizes, and minimum viable tests before full commitment. Produces `.agents/experiment-[name].md`. Not for strategic prioritization (use solution-design) or market sizing (use market-research).
9icp-research
Builds ideal customer profiles and buyer personas — analyzes demographics, pain points, jobs-to-be-done, and segmentation for a target market. Produces `.agents/mkt/icp-research.md`. Not for competitive positioning (use solution-design) or campaign planning (use imc-plan).
1