founder-validation-loop

Structures experiments into hypothesis, test, decision, and captured reusable assets.

1|Updated Jun 3, 2026
One-click install
npx skills add https://github.com/tanveerriaz/Skillz --skill founder-validation-loop-tanveerriaz
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: founder-validation-loop
Source: https://github.com/tanveerriaz/Skillz/tree/main/skills/founder-validation-loop
Command: npx skills add https://github.com/tanveerriaz/Skillz --skill founder-validation-loop-tanveerriaz

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Solo builders and founders run many experiments but lose the insights and reusable value, ending up with piles of abandoned prototypes and repeated work. This Skill turns each experiment into a deliberate test with a pre-set success bar, an honest keep/kill/pivot decision, and a captured reusable asset. ## Core Features & Use Cases - Hypothesis Framing: Forces a one-line falsifiable hypothesis with a defined success signal before any work begins. - Cheapest-Test Selection: Guides you to the least-effort valid test, such as a landing page or manual concierge version, instead of a full build. - Asset Capture: Extracts reusable templates, snippets, checklists, or lessons from every outcome, including kills. - Use Case: You have an idea for a skills marketplace. The Skill helps you define the hypothesis, run a one-page repo test with a 25-star bar, decide to keep it after 60 stars, and capture the repo structure as a reusable template. ## Quick Start Help me run a validation loop on my new product idea: define the hypothesis, pick the cheapest test, set the success bar, and capture what is reusable afterward.

Frequently Asked Questions about founder-validation-loop

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

FAQPage Schema
How do I validate a startup idea before building it?▼

State a one-line falsifiable hypothesis, then run the cheapest test that produces a real signal, such as a landing page or manual concierge version. Set the success bar in advance and decide keep, kill, or pivot based on the observed result.

What is the cheapest way to test a product hypothesis?▼

The cheapest valid tests are landing pages, manual concierge versions, or tiny prototypes rather than full builds. The goal is the least work that produces a real signal like usage, replies, or conversions.

When should I kill a side project or experiment?▼

Kill an idea when the observed signal falls below the success bar you set before running the test. Avoid sunk-cost reasoning, and still capture any reusable asset or lesson before moving on.

What should I do when experiment results are ambiguous?▼

Treat weak or ambiguous signals as inconclusive rather than forcing a decision. Design a sharper, more targeted test instead of rationalizing the result.

How do I reuse work from failed experiments?▼

Extract whatever is reusable after every outcome: code patterns, templates, checklists, or documented lessons. Even a killed idea yields a captured lesson that informs the next hypothesis.