Quirky Query Hub playbook · 2 minute read
Read all three components first
The browser builds the scenario, twist and constraint in sequence using Generate premise, Add twist and Add constraint. Read all three before collecting a continuation, then keep the established rule consistent as players add ideas. A twist creates a consequence; it is not permission to ignore an earlier detail.
For a paper storytelling variation, a host may collect a first response and reveal a hidden twist afterward. That delayed reveal is a different format. Do not tell players to search for a hidden-twist button in the current tool.
A concrete turn and its outcome
A scenario gives every door a different destination, a twist makes the doors follow the weather, and the constraint forbids changing the forecast. One player wants to reach the kitchen. Their continuation must work with those three facts: carrying a picnic through a sunny door is valid; inventing a weather-control machine erases the constraint.
Take the story through a full handoff
Read the complete combination, then let Alex contribute the opening action while Blair listens for continuity. Alex records a kitchen picnic reached through a sunny door. Blair can add a consequence consistent with the forecast rule, such as the route changing when a cloud arrives. Nobody can erase the rule by inventing a weather machine halfway through.
Save the continuation if the group wants to keep it, then move to a new combination or continue orally. A saved idea is not an automatic finished novel or a humor ranking. If the generated premise needs clarification, agree a meaning before the first response rather than penalizing a later player for the host's unstated interpretation.
A few good questions
When does the browser reveal the twist?
Use Generate premise, Add twist and Add constraint in order. A host-led delayed reveal is an optional paper variation.