vibeprompt

Kill Criteria Generator

Before starting any build, to define in advance the specific, measurable conditions under which you will stop working on this project and move on.

Submitted by @dotsystemsdevs

Prompt
Help me write kill criteria for my project before I start building. Kill criteria are the specific, measurable conditions under which I will stop working on this project and move on. Writing them now, before I'm emotionally invested, is the only time I can do it honestly.

My project: [DESCRIBE YOUR PROJECT]
My target user: [WHO IT'S FOR]
My planned launch timeline: [e.g. 6 weeks to MVP]
My available time per week: [e.g. 10 hours/week]

Generate kill criteria across these 4 dimensions:

1. TRACTION KILL CRITERIA: Define the minimum traction signals that must be present within a specific time window. Format each as: "If [measurable condition] is not met by [specific date or week number], kill the project." Examples of what to include:
   - Minimum number of signups or waitlist entries within X days of launch
   - Minimum number of users who complete the core value loop at least once
   - Minimum number of users who return for a second session within 7 days

2. REVENUE KILL CRITERIA (if applicable): If this is a paid product, define revenue thresholds. Format: "If [revenue condition] is not met by [date], kill the project." Be specific — not "some revenue" but "$X MRR by week N."

3. BUILD KILL CRITERIA: Define when the build itself signals the idea is wrong. Format: "If building [feature or function] requires more than [time/complexity] because [reason], this is a signal the approach is wrong and we should stop." Examples: if the MVP scope keeps expanding past 8 features, if no working prototype exists after 3 full weeks of work.

4. PERSONAL KILL CRITERIA: Define the personal conditions that would make continuing unethical or unsustainable. Example: "If I spend more than [$ amount] on infrastructure before the first paying user, stop."

Finally, write a KILL DECISION RULE: A single sentence that describes the process for actually making the kill decision. Who decides? How? Example: "If 2 or more kill criteria are triggered, I will make a final go/no-go decision within 48 hours and not continue working in the meantime."

Output all criteria as a checklist I can paste into my project doc.