investigate

Plan and conduct user research from interview guides through synthesis into actionable insights.

Updated Aug 20, 2026
One-click install
npx skills add https://github.com/ishfuseini/usecase-gen --skill investigate-ishfuseini
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: investigate
Source: https://github.com/ishfuseini/usecase-gen/tree/main/agent/skills/investigate
Command: npx skills add https://github.com/ishfuseini/usecase-gen --skill investigate-ishfuseini

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Design and product decisions often rest on assumptions rather than evidence. This Skill guides the full user research lifecycle — planning studies, choosing methods, writing interview guides and usability test plans, designing surveys, and synthesizing raw data into insights that drive decisions. ## Core Features & Use Cases - Research Planning & Method Selection: Decision frameworks for choosing between interviews, usability tests, surveys, diary studies, contextual inquiry, card sorts, tree tests, and analytics review based on what you need to learn. - Execution Guides: Templates for interview guides with probing techniques, usability test plans with severity ratings, and survey designs that avoid bias pitfalls like leading questions and double-barreled items. - Synthesis & Communication: Affinity mapping, Braun & Clarke thematic analysis, insight statements with evidence-strength grading, and findings reports structured as evidence pyramids. - Use Case: A product team unsure why onboarding completion is low uses this Skill to plan five contextual inquiries, synthesize findings via affinity mapping, and deliver a findings report with severity-rated issues and specific recommendations. ## Quick Start Ask the assistant to plan a user research study with an interview guide for understanding how customers currently solve a specific problem.

Frequently Asked Questions about investigate

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I choose the right user research method?

Start with what you need to learn, then match the method. Use interviews or contextual inquiry for generative questions, usability tests or surveys for validation, diary studies for behavior over time, and card sorts or tree tests for information architecture questions.

How many participants do I need for user interviews or usability tests?

Five to eight interviews typically reach thematic saturation for generative research. Five usability test participants per round catch roughly 85% of issues. Surveys need 100+ responses for descriptive statistics and 30+ per group for comparisons.

How do I write interview questions that avoid bias?

Ask about past behavior instead of hypotheticals, avoid leading or compound questions, and use open-ended prompts like "walk me through the last time you did X." Use silence and neutral probes such as "tell me more about that" rather than suggesting answers.

What is the difference between moderated and unmoderated usability testing?

Moderated testing lets you probe confusion and observe behavior live, suiting complex tasks and early concepts. Unmoderated testing is faster and cheaper with larger samples, best for straightforward evaluative tasks on stable prototypes.

How do I synthesize user research findings into insights?

Use affinity mapping to cluster observations bottom-up, then apply thematic analysis to name patterns. Structure each insight as observation plus inference plus implication, and tag it with an evidence strength rating of strong, moderate, or weak.

When should I not rely on qualitative research findings alone?

Small qualitative samples reveal patterns but not prevalence. Findings from five to eight interviews are hypotheses about frequency, so validate with surveys or analytics before making claims about how common a behavior is across your user base.