experiment-design-and-prioritization

Prioritize A/B test backlogs with ICE scoring and design experiments using Heatmap MCP data.

Updated May 6, 2026
One-click install
npx skills add https://github.com/Heatmap-com-Inc/heatmap-claude-skills --skill experiment-design-and-prioritization-heatmap-com-inc
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: experiment-design-and-prioritization
Source: https://github.com/Heatmap-com-Inc/heatmap-claude-skills/tree/main/skills/experiment-design-and-prioritization
Command: npx skills add https://github.com/Heatmap-com-Inc/heatmap-claude-skills --skill experiment-design-and-prioritization-heatmap-com-inc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? CRO teams struggle to decide which tests to run first, write testable hypotheses, and size experiments correctly for their traffic. This Skill turns a raw list of test ideas into a scored, sequenced roadmap grounded in real analytics data. ## Core Features & Use Cases - ICE Scoring with Data Inputs: Score Impact, Confidence, and Effort (1-5 each) using Heatmap MCP queries for page traffic, baseline RPS, and funnel drop-off rates instead of gut feel. - Hypothesis and Test Design Standards: Enforces a structured hypothesis format and a four-element test checklist covering audience, target page, MDE, sample size, and a Do No Harm guardrail. - Blanket vs. Targeted Decisions: Uses Quadrant-of-traffic baselines (new vs. returning, mobile vs. desktop) to decide whether a test should run sitewide or target a specific segment. - Use Case: A user asks "what should we test next on our checkout page?" Claude pulls funnel abandonment and element click data via MCP, scores the backlog with ICE, and returns a prioritized test roadmap with sample-size estimates. ## Quick Start Ask Claude to prioritize your CRO test backlog using ICE scoring with live Heatmap data for your site.

Frequently Asked Questions about experiment-design-and-prioritization

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

FAQPage Schema
How do I prioritize my A/B testing backlog?▼

Use ICE scoring: rate each hypothesis on Impact, Confidence, and Effort from 1 to 5, then sum them. Tests scoring 12 or higher are Priority 1. Ground Impact and Confidence scores in analytics data like page sessions, RPS, and funnel abandonment rather than intuition.

How much traffic do I need to run an A/B test?▼

At 95% significance and 80% power with a 50/50 split, detecting a 5% lift needs about 10,000 sessions per variant, 10% needs about 2,500, and 20% needs about 650. Low-traffic sites should test larger changes with a higher minimum detectable effect.

What makes a good A/B test hypothesis?▼

A good hypothesis names the specific element changed, the target page, the primary metric (RPS), the audience, the expected direction and magnitude of change, and cites at least one research data source. "Try a better hero image" is a direction, not a testable prediction.

When should I stop an A/B test early?▼

Stop early only when a predefined Do No Harm guardrail triggers, such as RPS dropping more than 15% below baseline with over 80% confidence the result is negative. Normal variance in the first week often shows negative swings that correct by day 14.

Should I run a blanket test or target a specific segment?▼

Start with a blanket test for new hypotheses when traffic supports multi-segment analysis within two weeks. Use a targeted test when one segment holds over 50% of sessions with significantly lower RPS, or when a prior blanket test showed a clear segment-specific effect.