agentleFS
zpower426zpower426/pmpowers/skills/lean-experimentation/SKILL.md

lean-experimentation

Skill0 starsChanged 7 months agoMITView on GitHub

Validate core assumptions at minimum cost. Proof of concept must be established through experimentation before investing in expensive R&D.

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Do not rush to build a full MVP.

    line 12

≈ “Common” is an estimate: at least 1 in 5 of the 308,232 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Lean Experimentation: Lean Validation and the RAT Protocol

Experimentation is not about proving you are right, but about reducing the risk of failure through lowest-cost learning.

Core Process: RAT (Riskiest Assumption Test)

Do not rush to build a full MVP. First identify: "If which one assumption is proven wrong, the entire product/feature becomes meaningless?" Design an experiment specifically for that assumption.

Checklist

  1. List All Preconditions (Identify Assumptions) — Covering Desirability, Feasibility, and Viability.
  2. Filter Riskiest Assumptions (Select RAT) — Choose those with the highest uncertainty and the greatest impact on success or failure.
  3. Match MVP Type — Refer to the "MVP Selection Matrix" below.
  4. Define Falsifiable Metrics — A clear success/failure value must be set in advance (e.g., Click-through Rate > 15%).
  5. Execute and Log Results — Experiment details are recorded in docs/pmpowers/experiments/.
  6. Decision (Pivot or Persevere) — Decide whether to stay the course, pivot entirely, or stop the project based on evidence.

MVP Selection Matrix

TypeUse CaseCost
Landing PageValidate demand authenticity and intent to click.Extremely Low
Smoke TestValidate if users are willing to pay for the feature or leave contact info.Low
ConciergeManually simulate AI or automated processes to validate service value.Medium
Wizard of OzFront-end looks automated, back-end is manually operated; validates complex interaction logic.Medium
Single Feature PrototypeValidate the usability of core functionality.High

Validation Loop Logic

digraph lean_cycle {
    "Identify Assumptions" [shape=box];
    "Design RAT" [shape=box];
    "Run Lean Experiment" [shape=box];
    "Learn from Data" [shape=box];
    "Assumption Holds?" [shape=diamond];
    "Persevere" [shape=doublecircle];
    "Pivot" [shape=doublecircle];

    "Identify Assumptions" -> "Design RAT";
    "Design RAT" -> "Run Lean Experiment";
    "Run Lean Experiment" -> "Learn from Data";
    "Learn from Data" -> "Assumption Holds?";
    "Assumption Holds?" -> "Persevere" [label="Yes"];
    "Assumption Holds?" -> "Pivot" [label="No"];
}

Delivery Standards

Experiment reports must include: Hypothesis, MVP Description, Success Metrics, Actual Data, and Conclusion.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

Reviews can't be read right now.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.