Skip to content
Back to skills

Pm Experiment

ASecurity

Design an A/B test, holdout, multivariate, or switchback experiment. Spawns experiment-designer. Output is gate-quality: pre-registered hypothesis, MDE, guardrails, stopping rules.

  • 3 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added September 22, 2026
ai-agentsgobashrails

Security analysis

A100/100

Pro scans all 2 files and shows the line behind each finding

Scanned September 22, 2026

npx -y skills add VandanaAjayDubey111/great-pm --skill pm-experiment --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Pm Experiment?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Pm Experiment
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/vandanaajaydubey111-pm-experiment/badge)](https://www.skillsdirectory.com/skills/vandanaajaydubey111-pm-experiment)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: pm-experiment
description: "Design an A/B test, holdout, multivariate, or switchback experiment. Spawns experiment-designer. Output is gate-quality: pre-registered hypothesis, MDE, guardrails, stopping rules."
---

## Codex host binding

- Treat references to Claude slash workflows as the equivalently named Codex skill.
- Before delegating to any specialist, read the `great-pm-runtime` skill and the selected packaged role file.
- Treat "invoke", "assign", "delegate", "spawn", and source Agent-tool instructions as a required Codex `spawn_agent` call with that role and a bounded assignment.
- For the spawn tool's `task_name` or `agent_name` identifier, replace canonical role-name hyphens with underscores (`query-refiner-pm` → `query_refiner_pm`). Keep canonical names unchanged in prompts, filenames, verdict logs, and user-facing output; this is an internal identifier mapping, not a role rename.
- Store every returned agent identifier. Never call a wait tool until a spawn has returned an identifier, and wait only on identifiers returned by successful spawns.
- If `spawn_agent` is unavailable or a spawn fails, report BLOCKED; do not impersonate the specialist or wait on an empty agent set.
- Resolve bundled paths from the installed GreatPM plugin root.
- Ignore Claude-only model aliases, colors, turn limits, and tool allowlists.
- Preserve GreatPM human gates, governance, state, and reporting contracts.


You are the great-pm `$pm-experiment` command. Author a pre-registered
experiment.

## Parse arguments

- **`<hypothesis-slug>`** (required) → kebab-case slug (e.g.
  `onboarding-shorter-flow`).
- **`--type=`** (optional, experiment-designer recommends if omitted).
  - `ab` — classic two-arm A/B.
  - `multivariate` — multiple factors.
  - `holdout` — one cohort doesn't get the change (for long-term effects).
  - `switchback` — time-sliced (for marketplace / two-sided experiments).

## Pre-flight

```bash
SLUG="${1:?usage: $pm-experiment <hypothesis-slug> [--type=...]}"
mkdir -p .great-pm/drafts
ls .great-pm/drafts/metrics-plan-*.md 2>/dev/null && echo "METRICS_EXISTS" || echo "NO_METRICS"
```

If `NO_METRICS` → WARN. Experiments without a pre-defined metrics plan
are HARKing (Hypothesising After Results Known). Recommend running
`$pm-metrics` first.

## Operating procedure

0. **Step 0 — refine the user's query** (transparent Mode B). Invoke
   `query-refiner-pm` with `$ARGUMENTS`. The refiner returns:
   ```
   You typed:  <original>

   Refined to: <refined brief>

   What changed: <one line>

   Proceeding with refined. Reply "use original" to override.
   ```
   Use the **refined** version as the brief for subsequent steps UNLESS
   the user replies "use original". Log the refinement to
   `.great-pm/refinements/$(date +%Y-%m-%d).log`. This wiring is
   universal across great-pm commands per the gate-policy: explicit
   discipline — you make the user's leverage visible while preserving
   their ability to override.

1. **experiment-designer**
   - Brief: author the experiment doc with:
     - **Hypothesis (one sentence with mechanism)** — "If we X, then Y
       will move by Z because mechanism." If the mechanism is hand-wavy,
       the result won't generalise.
     - **Primary metric** (must be pre-defined in metrics plan).
     - **MDE (minimum detectable effect)**.
     - **Guardrail metrics** (latency, errors, long-term retention).
     - **Test design** (type + justification + sample size + power + alpha).
     - **Pre-registered stopping rules** (no peeking before planned end).
     - **Risks** (novelty effect, seasonality, network effects).
     - Empty read-out section (DO NOT pre-fill).
   - Output: `.great-pm/drafts/experiment-<slug>.md` using
     `templates/EXPERIMENT-template.md`.

2. Status: `PLANNED` (not RUNNING, not COMPLETE).

3. Optional: file a Beads issue to track the experiment run:
   ```
   bd create --title="Run experiment: <hypothesis>" \
     --description="See .great-pm/drafts/experiment-<slug>.md" \
     --type=task --priority=2 --labels=experiment
   ```

## Reporting

- **DONE**: `DONE: $pm-experiment — experiment-<slug>.md (status: PLANNED). Type: <type>. Duration: <days>. Sample: <N> per arm.`
- **BLOCKED**: experiment-designer unavailable. tried + failed_because + need.

## Notes

- **Frame the hypothesis BEFORE running.** HARKing is forbidden.
- A "winning" primary with a broken guardrail is a regression in disguise.
- The read-out section stays empty until the experiment ends. Filling it
  early is a process violation.

Files in this skill

  • SKILL.md4.5 KB
  • agents/openai.yaml226 B

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.