Results for “hypothesis-testing”

Automated hypothesis generation and testing using large language models. Use this skill when generating scientific hypotheses from datasets, combining literature insights with empirical data, testing hypotheses against observational data, or conducting systematic hypothesis exploration for research discovery in domains like deception detection, AI content detection, mental health analysis, or other empirical research tasks.

Design, prioritize, and evaluate product experiments with clear hypotheses and defensible decisions, including A/B testing, sample size estimation, and statistical interpretation.

Frame an epic as a testable hypothesis with target user, expected outcome, and validation method. Use when defining a major initiative before roadmap, discovery, or delivery planning.

Stress-test a feature idea for an existing product by surfacing risky assumptions across Value, Usability, Viability, and Feasibility using multi-perspective devil's advocate thinking.

Design low-effort experiments to test product assumptions for an existing product, including prototypes, A/B tests, spikes, and other validation methods.

Stress-test ideas, plans, and decisions using structured critical reasoning across five modes: Socratic questioning, dialectic, pre-mortem, red teaming, and evidence audit.

Design lean startup experiments (pretotypes) for a new product by creating XYZ hypotheses and suggesting low-effort validation methods like landing pages, explainer videos, and pre-orders.

Design rigorous A/B tests with clear hypotheses, controlled variants, appropriate metrics, and sample size calculations.

Generate a Lean Canvas with sections for problem, solution, metrics, cost structure, UVP, unfair advantage, channels, segments, and revenue for testing business hypotheses.

Transforms A/B test and product experiment data into actionable readouts with hypothesis, metrics, interpretation, and decision.

When the user wants to plan, design, or implement an A/B test or experiment, or build a growth experimentation program. Also use when the user mentions "A/B test," "split test," "experiment," "test this change," "variant copy," "multivariate test," "hypothesis," "should I test this," "which version is better," "test two versions," "statistical significance," "how long should I run this test," "growth experiments," "experiment velocity," "experiment backlog," "ICE score," "experimentation program," or "experiment playbook." Use this whenever someone is comparing two approaches and wants to measure which performs better, or when they want to build a systematic experimentation practice. For tracking implementation, see analytics. For page-level conversion optimization, see cro.