How to use the Plot Hole Checker.
Look for missing causes and broken rules, not merely surprising events. A proposed fix should preserve the story's established constraints.
Make the workflow fit your task.
Track what a character knows, what access they have and which rules apply at each event. Flag the missing cause, then propose the smallest revision that restores the established chain of events.
- What you provide
- Story synopsis or manuscript excerpt.
- What you get
- Continuity and causal gaps with repair options.
See the input and the result.
Illustrative input and output · a teaching example, not a live WebAct run
Example input
The locked vault has one key, but a character enters without it or an explained alternative.
Completed example
Continuity gap: the entry scene conflicts with the established one-key access rule. Possible repairs: establish another access route earlier, show the key changing hands, or revise the entry scene. The supplied story does not establish which repair is intended; none is treated as an existing fact.
Load this input into the prompt, then copy it to WebAct to try the task. Your result may differ from the illustration.
Decisions and troubleshooting.
Is an unexplained event automatically a plot hole?
It may be an intentional mystery. Check whether the story later supplies a compatible explanation and whether the reader is meant to notice the gap.
Why does one fix create another inconsistency?
Trace the changed fact through later scenes. A new key, power or clue can alter several decisions beyond the flagged moment.
Try it with your own source.
Replace the example with your material in the task prompt. Keep the requirements you need, then copy the task into WebAct.
Customize and copy the task ↑