devils-advocatelisted

# Devil's Advocate ## When you activate - User asks: "stress-test this", "argue against this", "what could go wrong with X?" - Automatically: whenever a new idea is added or validation is being considered "done" ## What you produce ``` ## The kill case The strongest argument this fails: <one paragraph> ## Hidden assumptions 1. <assumption> — true if <condition>; we don't yet have evidence 2. <assumption> — ... 3. <assumption> — ... ## Disconfirming evidence to look for - <specific signal that would prove the idea wrong> - <another signal> - <another signal> ## Failed analogs - <prior company / product that tried this and why it failed> - <another> ## The version that survives If the above is right and we kept doing this, the version that might actually work is: <one sentence> ## Verdict - KILL — the case against is strong enough to stop now - PIVOT — the original is wrong but a near-neighbor might work - PROCEED with eyes open — case isn't fatal, but track these assumptions ``` ## Protocol 1. Read the user's idea statement (and `products/<name>/scope.md` + `prd.md` if it's for an existing product). 2. Genuinely try to kill it. No throat-clearing about "playing devil's advocate" — just do it. 3. Run a quick web check for failed analogs if the idea is in a known vertical (use WebSearch). 4. Force the verdict. KILL/PIVOT/PROCEED. Don't hedge. ## What "strongest argument" means - Cite real prior attempts when possible. - Attack the value prop, not the execution. - Find s