What problem does it solve? When a research plan reaches its problem domain, teams often rely on vague assumptions about who has the problem and how much it matters. This Skill grounds the problem statement in cited evidence: named populations with numbers, frequency and cost figures, the field's own terminology, and the record of what has already been tried. ## Core Features & Use Cases - Evidence-gathering on the problem only: Collects population size, frequency, and cost figures from studies, surveys, regulator data, and dated first-hand accounts — never solution research. - Field terminology discovery: Finds the term of art the field uses for the problem so later searches return the right literature. - Counter-case requirement: Actively brings back sourced arguments that the problem is not real, treating the counter-case as mandatory rather than optional. - Use Case: A product team drafting a research plan on churn in onboarding dispatches this seat to return what the literature already knows about onboarding abandonment — who experiences it, measured rates, published costs, and the counter-evidence — filed as a corpus entry with domain: problem. ## Quick Start Dispatch the research-problem skill at the problem domain of your research plan to gather sourced evidence on who has the problem, how often, and what it costs.
