meta-experiment

Design, run, and interpret controlled experiments to validate software changes.

2|3|Updated Oct 20, 2025
One-click install
npx skills add https://github.com/psd401/psd-claude-coding-system --skill meta-experiment
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: meta-experiment
Source: https://github.com/psd401/psd-claude-coding-system/tree/main/plugins/psd-claude-coding-system/skills/meta-experiment
Command: npx skills add https://github.com/psd401/psd-claude-coding-system --skill meta-experiment

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a rigorous, repeatable framework to design, run, and interpret controlled experiments that validate software changes before deploying them broadly.

Core Features & Use Cases

  • Experiment lifecycle: design, deploy, run, analyze, and decide with auto-promotion or rollback based on statistical results.
  • Safety and rigor: enforces minimum sample size, significance thresholds, and rollback when regression is detected.
  • Operational integration: tracks metrics across experiments, stores results, and supports both manual and automated workflows.

Quick Start

To design a new experiment, use a command like /meta-experiment create --hypothesis "<your-hypothesis>" --sample-size 10; to monitor progress, run /meta-experiment status; to analyze results, run /meta-experiment analyze exp-<id>; to auto-manage experiments, run /meta-experiment --auto

Frequently Asked Questions about meta-experiment

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

FAQPage Schema
How do I run A/B tests with statistical significance to validate software changes?

A/B testing with statistical significance involves designing controlled experiments that compare variants, collecting metrics, and analyzing results against a p < 0.05 threshold. This Skill automates the full lifecycle—from hypothesis creation through deployment decisions—ensuring minimum sample sizes and rigorous statistical validation before rollout.

What's the best way to decide whether to deploy or rollback a software change?

Use controlled experiments to measure the impact of changes against control groups. This Skill analyzes experimental results with statistical rigor, automatically promoting changes when they meet significance thresholds or triggering rollback when regression is detected, removing guesswork from deployment decisions.

Do I need to manually monitor experiment results or can it be automated?

Both workflows are supported. You can manually run commands to check experiment status and analyze results, or enable auto-management to track metrics, enforce safety thresholds, and automatically promote or rollback based on statistical outcomes without manual intervention.

What safeguards prevent deploying changes that harm user experience?

This Skill enforces minimum sample size requirements, statistical significance thresholds (p < 0.05), and automatic rollback when metrics show regression. These safeguards ensure only validated changes reach production and problematic variants are caught before broad deployment.

How do experimental design and sample size affect my deployment confidence?

Proper experimental design and adequate sample size determine whether statistical results are reliable. This Skill requires you to specify both upfront, enforcing minimums to prevent underpowered experiments that might miss real regressions or produce false positives.