investigate

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

Updated Jul 21, 2026
One-click install
npx skills add https://github.com/rakedzior/rootine --skill investigate-rakedzior
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: investigate
Source: https://github.com/rakedzior/rootine/tree/main/.agents/skills/investigate
Command: npx skills add https://github.com/rakedzior/rootine --skill investigate-rakedzior

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: Structured templates for interview guides, usability test plans with severity ratings, and bias-free survey design with sample size guidance. - Synthesis & Communication: Affinity mapping, Braun & Clarke thematic analysis, insight statements with evidence strength grading, and findings report templates. - Use Case: A product team unsure why onboarding completion is low uses this Skill to plan five moderated usability tests, write task scenarios, rate issue severity, and deliver a findings report with prioritized recommendations. ## Quick Start Ask the AI to write an interview guide for understanding how users currently track their project status, including probing questions and a closing script.

Frequently Asked Questions about investigate

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

FAQPage Schema
How do I write a user interview guide?▼

Structure the guide in three parts: a 5-10 minute opening with consent and rapport building, 30-40 minutes of open-ended behavior-focused core questions with probes, and a closing summary. Avoid leading questions, hypotheticals, and asking participants to design solutions.

How many participants do I need for usability testing?▼

Five participants per round typically uncover about 85% of usability issues. Run multiple small rounds rather than one large study, and pilot test every task with a colleague before the real sessions.

What sample size do I need for a survey?▼

Use 100+ responses for descriptive statistics and 300+ for segment-level analysis. For group comparisons, aim for at least 30 responses per group, and always report your sample size alongside any percentage.

When should I use interviews versus surveys?▼

Use interviews for generative questions when you do not know what to ask yet, since they reveal motivations and mental models. Use surveys for evaluative questions when you have a hypothesis and need to measure prevalence at scale.

How do I synthesize user research findings?▼

Use affinity mapping to cluster observations bottom-up without preset categories, or follow Braun and Clarke's six-step thematic analysis. Structure each insight as observation plus inference plus implication, and tag it with an evidence strength rating.

What are the limitations of small-sample qualitative research?▼

Small samples reveal patterns but not prevalence, so findings from 5-8 interviews should be presented as signals, not statistics. Triangulate across multiple methods and flag uncertainty rather than generalizing to all users.