idea-validator

# Idea Validator A structured way to find out whether an idea deserves to be built **before** you build it — by attacking the one assumption that is both most likely to kill the project and cheapest to test, instead of polishing the parts that were never in doubt. The whole skill compresses to one sentence: > **Validate the riskiest, cheapest-to-test assumption first — not the easiest component first.** Everything below is in service of that ordering. --- ## The failure this exists to prevent Picture a representative failure — the kind this skill exists to prevent. The diagnosis is worth internalizing, because the trap is seductive and almost invisible from the inside: A project applies **rigor lavishly to execution** — clean code, a governance model, an open protocol, a conformance suite, falsifiable experiments — and applies it to the **premise far too late**. It de-risks the parts that were never in doubt ("can we build a clean version of this?" — yes, trivially) and leaves the load-bearing doubt untouched until dozens of commits in: *"is this actually better than what already exists?"* The answer, available on day one from a single web search, is no — the core mechanic is a commodity that several established products already ship. Almost everything built gets deleted later. The lesson is not "be less rigorous." It is **rigor in the wrong order is expensive rigor.** The riskiest assumption is almost never the engineering. It is usually the market/premise question ...