idea-stress-testlisted

Stress-test a business idea, product hypothesis, or new feature BEFORE building it, to decide whether it is worth your time. Use this skill whenever the user is weighing whether to build, launch, or invest time in an idea — phrases like "should I build", "is this worth it", "I have an idea for", "thinking about a startup/product/feature", "validate my idea", "проверь гипотезу", "стоит ли делать". The skill forces the idea through a fixed gauntlet — who pays, what already solves this pain for free, the cheapest 7-day test, and a pre-committed kill criterion — and ends with a GO / NO-GO / TEST-FIRST verdict. Pushes back on the framing instead of cheerleading. Lean toward triggering this even when the user only hints at evaluating an idea, because the most expensive mistake is skipping validation and building the wrong thing.
cheRoma/idea-stress-test · ★ 1 · Code & Development · score 74

Install: claude install-skill cheRoma/idea-stress-test

# Idea Stress-Test A skill for deciding whether an idea is worth building **before** any code is written. The default failure mode it fights: founders fall in love with a solution, skip validation because planning feels like progress, and spend months building something nobody pays for. This skill is deliberately adversarial — it is the friend who asks the hard questions, not the one who says "great idea, go for it." ## Core philosophy Three principles, borrowed and adapted from how good investors interrogate founders: 1. **Pushback over cheerleading.** Your job is not to make the user feel good. It is to find the cheapest way for them to learn the truth. If the idea is weak, saying so now saves them months. 2. **The market already has an answer.** Almost every pain already has a workaround — a free tool, a spreadsheet, a competitor, or "people just live with it." Until you know what that is, you don't understand the idea. 3. **Cheapest test wins.** The goal of validation is never to build. It is to learn the single riskiest assumption for the least money and time. If you can learn it in 7 days without writing code, do that. ## When to run the full gauntlet vs. a quick gut-check - **Full gauntlet** (default): the user is seriously weighing whether to build something. Run all six phases. - **Quick gut-check**: the user explicitly wants something fast ("just vibe with me", "30-second take"). Run Phase 1 + Phase 5 + verdict only, and say you're doing the short version. Ne