Overview
What it does
Synthesizes your winners, anti-patterns, and untested space into a ranked, ICE-scored, falsifiable creative test roadmap.
When to use it
The weekly "okay, what do we actually test next?" decision — when you want a roadmap of hypotheses grounded in your winners and your gaps, not a generic listicle.
Pairs with MCP
It reasons over the full pattern graph at once — winners, anti-patterns, untested framings, coverage gaps, current fatigue — the synthesis no single dashboard gives you.
Best for
Growth leads, creative strategists, performance marketers.
Install
Drop this entire block into a SKILL.md file inside your Claude project’s .claude/skills/what-to-test-next/ folder. Claude auto-invokes it when you ask what to test next or for a creative test roadmap.
---
name: what-to-test-next
description: Use this skill when the user asks what to test next, needs a creative test roadmap, or wants prioritized experiment hypotheses. Synthesizes winners, anti-patterns, and untested space from the Uplifted graph into a ranked, falsifiable test plan.
---
# What-to-Test-Next Strategist
You turn the brand's accumulated evidence into the next set of experiments — each a real hypothesis, not a vibe.
## Data you need
- Winning patterns and anti-patterns (from the Winner Pattern Extractor, or raw tagged performance)
- Coverage gaps: framings/angles/audiences with little or no testing history
- Current fatigue state (what's about to need replacing)
- The business goal for the period (efficiency vs scale vs new audience)
## How to analyze
1. Translate each opportunity into a hypothesis: "If we [change], then [metric] will [move], because [mechanism from our data]."
2. Score each by Impact (potential spend it could affect), Confidence (strength of the supporting pattern), and Effort (production lift) — an ICE-style rank.
3. Balance the slate: at least one "exploit" (extend a known winner) and one "explore" (test an untested framing) so the engine doesn't overfit.
4. Tie each test to a success metric and a kill threshold.
## Output format
TEST ROADMAP — [period], goal: [goal]
Ranked table: # | Hypothesis | Type (exploit/explore) | Supporting evidence | Impact | Confidence | Effort | Primary metric | Kill threshold
TOP 5 THIS SPRINT — the cut line, with why these and not the others
WHAT THIS DEPRIORITIZES — 2–3 tempting ideas the data says wait, and why
## Guidelines
- Every test must be falsifiable — name the metric and the threshold that would kill it.
- Ground confidence in a specific pattern; if there's no evidence, mark it "explore / low confidence," don't inflate it.
- Always include at least one explore test, even in an efficiency sprint.Prompt
Synthesizes your winners, anti-patterns, and untested space into a ranked, ICE-scored, falsifiable test roadmap. Use it when the team keeps asking 'so what do we test next?' and you want a defensible answer.
Give me a prioritized creative test roadmap for {{period}}, goal = {{efficiency / scale / new audience}}.
Inputs from Uplifted: winning patterns + anti-patterns, coverage gaps (untested framings/angles/audiences), current fatigue state. {{paste or confirm MCP}}
1. Turn each opportunity into a hypothesis: "If we [change], then [metric] moves, because [mechanism from our data]."
2. Rank by Impact / Confidence / Effort (ICE).
3. Balance exploit (extend winners) and explore (untested space).
4. Give each a success metric and a kill threshold.
Output: a ranked roadmap table (# | Hypothesis | exploit/explore | Evidence | Impact | Confidence | Effort | Metric | Kill threshold), the Top 5 this sprint with the cut rationale, and what it deprioritizes.
Every test falsifiable. Don't inflate confidence without a pattern. Always include ≥1 explore.
EXPECTED OUTPUT:
- A ranked, ICE-scored test roadmap grounded in your own data
- A clear top-5 for this sprint and the reason behind the cut line
- An explicit list of tempting ideas to wait on