Players will want another version if the idea is understandable in under a minute, emotionally distinct, and produces at least one genuinely arguable design choice.
Success Criteria
- ✓ Players explain the core idea without help
- ✓ Players react emotionally: laugh, tense up, get curious, or complain usefully
- ✓ Players identify at least one thing they'd change
- ✓ Players ask what version 2 would look like
- ! The core mechanic may be more interesting in theory than in play
- ! Scope may creep during generation — one interaction, not five
- ! Player assumption mismatch: they may expect more polish than a Spark delivers
⬡ The Skeptic
Kindly stabbing the idea before reality does.
Failure Modes
- ✕The core of "A cooking game where recipes are prophecies. If you mess up a recipe, you are cursed (e.g. move more slowly, can't read ingredients, etc.)" may feel more novel to the creator than to a first-time player
- ✕Novelty wears off after one interaction if the mechanic isn't tactically meaningful
- ✕The idea may be a flourish without an underlying gameplay loop
Assumptions
- ?Players will engage with the concept on its own terms
- ?The mechanic communicates itself without instructions
- ?A story format is actually the right fit for this idea
Counterargument
A simpler, more conventional version of this concept might be cleaner and more replayable. The unusual framing needs to earn its complexity.
Toy Versions
v1Story Toy— Generated from: "A cooking game where recipes are prophecies
6/20/2026v2Story Toy— Watch whether players treat the recipe as a rule to game or
6/21/2026v3Story Toy— Watch whether players feel the curse consequences are fair p
6/21/2026v4Story Toy— Watch whether players try to negotiate with ingredients befo
6/23/2026Latest Feedback
InconclusiveFun 2.3 · Novelty 3.7→ View full summary
Lab Notes (1)
Dano DeBroux6/21/2026
Interesting spark.