ds-experiment-design

Design A/B experiments with causal structure, aligned units, and decision rules.

6|Updated Apr 9, 2026
One-click install
npx skills add https://github.com/Khodzitcky-Vl/data-science-ai-superpowers --skill ds-experiment-design
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ds-experiment-design
Source: https://github.com/Khodzitcky-Vl/data-science-ai-superpowers/tree/main/ds-experiment-design
Command: npx skills add https://github.com/Khodzitcky-Vl/data-science-ai-superpowers --skill ds-experiment-design

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents broken or uninterpretable A/B test results by forcing clear causal setup for hypothesis, randomization, metrics, guardrails, and decision rules before analysis begins.

Core Features & Use Cases

  • Causal-first experiment specification: Aligns treatment, exposure, observation, interference risks, and the metrics that should move when the business outcome improves.
  • Correct unit alignment checks: Validates that the randomization unit, exposure unit, and metric denominator match so results aren’t biased by aggregation mistakes.
  • Guardrails and failure-mode planning: Identifies leakage, interference, denominator drift, missing data, novelty effects, and operational constraints that can invalidate conclusions.
  • Decision rule readiness: Defines effect size targets, confidence/p-value policy, minimum detectable effect, and practical significance so stakeholders can act on outcomes.

Quick Start

Use ds-experiment-design to create a complete experiment plan for an A/B test of a pricing or ranking change, including hypothesis, unit of randomization, primary/guardrail metrics, key failure modes, and a clear decision rule.

Frequently Asked Questions about ds-experiment-design

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

FAQPage Schema
How do I design an A/B test that produces trustworthy causal conclusions?

A/B test design requires aligning treatment, exposure, observation, and randomization units to establish correct causal structure before analysis begins. You must specify hypothesis, population, time window, and metric hierarchy to prevent invalid conclusions.

How do I set up guardrails and identify failure modes for an A/B test?

Setting up guardrails involves identifying leakage, interference, denominator drift, missing data, and novelty effects that can invalidate A/B test results. Planning for these failure modes ensures operational constraints and metric invariants protect your experiment.

What is the best way to align randomization units with metric denominators?

The best way to align randomization units is to validate that the randomization, exposure, and metric denominator match exactly. This prevents biased A/B test results caused by aggregation mistakes and ensures correct causal interpretation.

How do I define a decision rule for minimum detectable effect and practical significance?

Defining a decision rule requires specifying effect size targets, confidence interval and p-value policy, minimum detectable effect, and practical significance. This readiness allows stakeholders to act on A/B test outcomes without ambiguity.

Can I use quasi-experiment design for product and pricing changes without full randomization?

Yes, quasi-experiment design applies to product, funnel, ranking, availability, or pricing changes where interpretation depends on randomization and metric design. It forces clear causal setup even when full randomization is not possible.

Why does my A/B test result show invalid conclusions despite statistical significance?

Invalid A/B test conclusions often happen when causal structure is misaligned, such as mismatched randomization and exposure units, or unaddressed interference and denominator drift. Forcing clear hypothesis and guardrail planning before analysis prevents this.