agentleFS
AdhamxonAdhamxon/claude-code-skills/.claude/skills/brainstorm-experiments-new/SKILL.md

brainstorm-experiments-new

Skill2 starsChanged 3 months agoMITView on GitHub

Design lean startup experiments (pretotypes) for a new product. Creates XYZ hypotheses and suggests low-effort validation methods like landing pages, explainer videos, and pre-orders. Use when validating a new product idea, creating pretotypes, or testing market demand.

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈7

    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:

    Create XYZ hypotheses and design pretotype experiments to validate a new product concept with minimal effort.

    line 8
  2. Distinctive:

    If the user provides files (market research, landing page mockups), read them first.

    line 14
  3. Distinctive:

    Landing Page: Test interest by measuring sign-ups or clicks

    line 24
  4. Distinctive:

    Explainer Video: Test understanding and appeal through engagement metrics

    line 25
  5. Distinctive:

    Email Campaign: Test demand through response and click-through rates

    line 26
  6. Distinctive:

    Pre-Order / Waitlist: Test willingness to pay through skin-in-the-game commitment

    line 27
  7. Distinctive:

    Skin-in-the-Game: Test willingness to pay — not just interest.

    line 31

≈ “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 Lean Startup Experiments (New Product)

Create XYZ hypotheses and design pretotype experiments to validate a new product concept with minimal effort.

Context

You are helping validate a new product concept: $ARGUMENTS using lean startup methodology.

If the user provides files (market research, landing page mockups), read them first.

Instructions

  1. Create an XYZ Hypothesis in the form: "At least X% of Y will do Z"
    • X%: The percentage of the target market expected to engage
    • Y: The specific target market (e.g., "mid-size luxury sedan buyers")
    • Z: How they will engage with the product
  2. Suggest 2-3 pretotype experiments to test the hypothesis with minimal effort. Consider:
    • Landing Page: Test interest by measuring sign-ups or clicks
    • Explainer Video: Test understanding and appeal through engagement metrics
    • Email Campaign: Test demand through response and click-through rates
    • Pre-Order / Waitlist: Test willingness to pay through skin-in-the-game commitment
    • Concierge / Manual MVP: Deliver the service manually to test value
  3. Key principles (Alberto Savoia, The Right It):
    • Skin-in-the-Game: Test willingness to pay — not just interest. Real commitment (time, money, reputation) is the only reliable signal.
    • Your Own Data (YODA): Collect your own data through experiments rather than relying on Others' Data (ODP) like market reports or analogies. "The market for your idea does not care about the market for someone else's idea."
    • Measure actual behavior, not users' opinions
  4. For each experiment, specify the hypothesis being tested, the method, the metric, and the success threshold.

Think step by step. 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.