market-research
No SKILL.md available for this skill.
View on GitHubMore from hungv47/research-skills
problem-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). For market-level trends and competitive context, see market-research. For testing hypotheses with experiments, see experiment.
9icp-research
Builds ideal customer profiles and buyer personas — analyzes demographics, pain points, jobs-to-be-done, and segmentation for a target market. Produces `research/icp-research.md`. Not for competitive positioning (use prioritize) or campaign planning (use campaign-plan). For brand identity from audience data, see brand-system. For market sizing and competitor landscape, see market-research.
9experiment
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). For diagnosing root causes, see problem-analysis. For campaign planning, see imc-plan.
7content-research
Researches what short-form content to create — competitor ads, audience communities, trending topics, viral patterns, scroll-stop creative across social, ad, SMS, and OOH channels. Produces `.agents/mkt/content-research.md`. For long-form research (blog, case study, byline, PR, newsletter, app store listings) use content-research-long instead. Not for market landscape (use market-research) or audience personas (use icp-research). For writing the content itself, see content-short.
6prioritize
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/prioritize.md`. Not for diagnosing what the problem is (use diagnose) 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.
1