investigate

Plans and conducts user research from interview guides through synthesis into actionable insights.

Updated Aug 26, 2026
One-click install
npx skills add https://github.com/danieliudi/trackforge-os --skill investigate-danieliudi
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: investigate
Source: https://github.com/danieliudi/trackforge-os/tree/main/.cursor/skills/investigate
Command: npx skills add https://github.com/danieliudi/trackforge-os --skill investigate-danieliudi

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 stakeholders can act on. ## Core Features & Use Cases - Research Planning & Method Selection: Decision frameworks for choosing between interviews, usability tests, surveys, diary studies, contextual inquiry, card sorts, and tree tests based on what you need to learn. - Interview & Test Instruments: Structured templates for interview guides with probing techniques, usability test plans with severity ratings, and bias-free survey design. - Synthesis & Reporting: Affinity mapping, Braun & Clarke thematic analysis, insight statements with evidence-strength grading, and findings reports with actionable recommendations. - Use Case: Your team debates whether users need a new dashboard feature. Use this Skill to plan five contextual interviews, write the discussion guide, synthesize the transcripts into themes, and deliver a findings report with evidence-strength ratings that settles the debate. ## Quick Start Ask the assistant to plan a user research study and write an interview guide for validating your product idea with five target users.

Frequently Asked Questions about investigate

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

FAQPage Schema
How do I plan a user research study?

Start by defining what you need to learn, then select a method that answers it: interviews for generative understanding, usability tests for evaluation, surveys for quantitative validation. The Skill provides a method comparison table with sample sizes, durations, and decision frameworks.

How do I write a user interview guide?

Structure it as opening (consent and rapport), core questions (broad behavior-focused questions with probes), and closing (summary and missed topics). Avoid leading questions, hypotheticals, and asking participants to design solutions.

How many participants do I need for usability testing?

Five participants per round catch roughly 85% of usability issues. For surveys, aim for 100+ responses for descriptive statistics and 30+ per group for comparisons. Diary studies typically need 10-15 participants.

What is the difference between generative and evaluative research?

Generative research (interviews, contextual inquiry) explores the problem space when you don't know what to ask. Evaluative research (usability tests, surveys) assesses specific solutions or hypotheses. Don't evaluate before you've generated.

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.

What are the limitations of small-sample qualitative research?

Small samples reveal patterns but not prevalence, so findings from 5-8 interviews are hypotheses, not statistics. The Skill requires flagging sample sizes, distinguishing observation from inference, and recommending quantitative follow-up when representativeness matters.