Genre promise check: are the expected scenes there
When to use it
Before the finale or at an arc's end: which scenes the genre promised are missing.
Fill in the variables
Assembled prompt
526The instruction exceeds 500 characters; the free run applies only the beginning. Copying applies the whole prompt.
Free runs use the fast model and return a short preview (about 300 words). Only the first ~1,000 words of manuscript are read.
How to use this prompt
- 1Fill in the variables
Enter your manuscript, characters or situation in the fields below. The example values are hints.
- 2Check the assembled prompt
The prompt is assembled below with placeholders filled. Edit any rule to fit your work.
- 3Copy it or run it
Copy it into the tool you already use, or run it in SparkLore for a short preview.
- 4Revise the result into your manuscript
The output is a draft. Follow the tips and rewrite half of it by hand.
How to get the most from it
- Compare with the must-have scenes in SparkLore's genre data (studio genre tab) for a sharper list.
- 'Weakly present' is the real problem. Missing scenes can be added; weak ones must be rewritten.
Use it with
- CritiqueCliche detector for this genre
Filter out the lines and beats that make genre readers say 'this again?'.
- Web novelHook table for a 16-episode arc
Planning the first 16-chapter arc of a serial: one table of why readers open each chapter and where you cut it.
- CharacterThe villain's case: a world where they are right
The antagonist is evil because the plot needs one. Build one the reader is briefly persuaded by.
Use it in the studio with your story bible
Sign up and get full-length results with free credits.
Sign up free and continue