Research

Growth experiment design — structure a growth hypothesis, define metric, baseline, expected lift, and kill condition for a single experiment. Use when asked to "design a growth experiment", "test this growth idea", "experiment framework", "how do we test if this works", or "growth hypothesis".

Survey existing privacy and legal docs for completeness and GDPR compliance. Use when asked to "audit our privacy docs", "are we GDPR compliant on paper", or "what legal docs are missing".

Survey product features and data flows for regulatory exposure. Use when asked to "survey our regulatory exposure", "map our data flows", or "what regulations apply to us".

Trademark clearance research and filing preparation for a name or mark. Use when asked to "clear this trademark", "can we use this name", or "prepare a trademark filing".

Survey project IP assets — trademarks, patents, OSS licenses, assignments. Use when asked to "survey our IP assets", "what trademarks do we hold", or "inventory our IP".

Open source license compliance audit — flag GPL, LGPL, AGPL, copyleft risks. Use when asked to "check our open source licenses", "do we have GPL risk", or "run an OSS license audit".

Use when asked to analyze a funnel, find where users drop off, diagnose low conversion or activation rates, design a metrics framework, set up OKRs, or measure whether a feature is working. Examples: "analyze our funnel", "why is activation low", "where are users dropping off", "design OKRs for this quarter", "is this feature working", "set up metrics for this launch".

A/B test design — produce an experiment spec with hypothesis, primary metric, MDE, sample size, run time, and decision rule. Also determines when NOT to A/B test and what to do instead. Use when asked to "design an A/B test", "should we test this", "experiment design", "how do we know if this works", "what's the sample size", or "set up an experiment".

Survey pending and required regulatory filings. Use when asked "what filings are due", "survey our regulatory filings", or "are we behind on filings".

Design a compromise assessment — hunting scope, methodology, and evidence collection. Use when asked "are we compromised", "run a compromise assessment", or "scope a threat hunt".

Product landscape reconnaissance — survey existing briefs, research, strategy, and team output before writing new briefs or dispatching specialists. Use when asked to "understand the product state", "what briefs exist", "what has the team produced", "orient me on this product", or before starting a new product initiative.

Survey corporate documents — articles, bylaws, cap table, board resolutions. Use when asked to "survey our corporate documents", "check cap table hygiene", or "what governance docs exist".

Design an A/B test — power analysis, randomization, and success metrics. Use when asked to "design an A/B test", "how many users do we need", or "run a power analysis".

User researcher — interviews, personas, Jobs-to-Be-Done, and customer feedback synthesis. Use when asked to "run user interviews", "build personas", "synthesize feedback", or "find the job-to-be-done".

User segmentation and persona creation from mixed data sources — analytics, CRM, support tickets, reviews, or any combination. Use when asked to "build personas", "who are our users", "segment our users", "create user profiles", "define user archetypes", or "who is the target user".

User research reconnaissance — survey existing personas, research docs, interview notes, and feedback artifacts to establish what is already known about users. Use when asked to "what research exists", "review existing personas", "what do we know about our users", or before starting new research or synthesis work.

Jobs-to-Be-Done analysis — given a product, user descriptions, transcripts, or tickets, produce a JTBD job map with switching forces analysis and opportunity ranking. Use when asked to "find the JTBD", "what jobs are users hiring us for", "job mapping", "what are users really trying to do", "JTBD framework", or "why are users switching".

Run a user interview — produce an interview guide and synthesize the output into an actionable insight report. Use when asked to "run a user interview", "synthesize these interview notes", "what do users actually want", "build a persona from this feedback", "find the JTBD in these transcripts", or "analyze this interview data".

Feedback synthesis — cluster support tickets, NPS verbatims, app store reviews, and churn surveys by theme, separate signal from noise, and produce an actionable insight report. Use when asked to "synthesize this feedback", "analyze support tickets", "what are users complaining about", "NPS analysis", "churn feedback synthesis", or "what's the feedback telling us".

Survey all user-facing strings in a codebase — map coverage and find gaps. Use when asked "what user-facing strings do we have", "map our copy coverage", or "find hardcoded strings".

Legal research on a specific question — case law, statutes, regulatory guidance. Use when asked to "research this legal question", "what does case law say", or "find the relevant statute".

Survey open legal questions and research gaps in the project. Use when asked "what legal questions are open", "where are our research gaps", or "list unresolved legal issues".

Audit existing resilience — identify untested failure modes and chaos engineering gaps. Use when asked "how resilient are we", "what failure modes are untested", or "find our chaos engineering gaps".

Design a chaos engineering experiment — hypothesis, blast radius, steady state, and abort conditions. Use when asked to "design a chaos experiment", "inject a failure", or "test the resilience of this service".