agentleFS
Sign inStart free
yuusakuriyuusakuri/agent-skills/skills/brainstorm-experiments-existing/SKILL.md

brainstorm-experiments-existing

Skill2 starsChanged 10 days agoMITView on GitHub

Design experiments to test assumptions for an existing product — prototypes, A/B tests, spikes, and other low-effort validation methods. Use when validating assumptions, testing feature ideas cheaply, or planning product experiments.

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    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:

    If the user provides files (PRDs, assumption lists, designs), read them first.

    line 14
  2. Distinctive:

    Test responsibly — don't put users or the business at risk

    line 32

≈ “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

Design Experiments (Existing Product)

Design low-effort experiments to test product assumptions before committing to full implementation.

Context

You are helping a product team design experiments for $ARGUMENTS. The team has a feature idea and assumptions that need validation.

If the user provides files (PRDs, assumption lists, designs), read them first.

Instructions

The user will describe their idea and assumptions. Work through these steps:

  1. Clarify the idea and assumptions: Confirm what the team wants to build and what they need to validate.
  2. Suggest experiments for each assumption. Consider methods like:
    • First-click testing or task completion with a prototype
    • Feature stubs or fake door tests
    • Technical spikes
    • A/B tests on production (with risk mitigation)
    • Wizard of Oz approaches
    • Survey-based validation (behavioral, not opinion-based)
  3. Key principles to follow:
    • Measure actual behavior, not users' opinions
    • Test responsibly — don't put users or the business at risk
    • For production tests (e.g., A/B tests), explain risk mitigation strategies
    • Aim for maximum validated learning with minimal effort
  4. For each experiment, specify:
    • Assumption: What do we believe?
    • Experiment: What exactly will we do to validate it?
    • Metric: What will be measured?
    • Success threshold: The expected value if we are right

Think step by step. Present experiments in a clear table or structured format. Save as markdown if substantial.

Further Reading

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.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

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.

Check your setup, free