Editing2026-09-28

Chapter continuity notes: what the next chapter must remember

When to use it

Right after posting a chapter: extract the states the next chapter will get wrong (time, injuries, items, promises).

Fill in the variables

Chapter{{manuscript}}

Assembled prompt

576

From the chapter below, extract the states the next chapter must remember.
Format (one line per item, omit empty ones):
- Time and date at chapter end
- Location of each major character at the end
- Physical state: injuries, exhaustion, drunkenness
- Possessions: gained, lost, handed over
- Promises and deadlines
- Knowledge: who newly knows what (and who still does not)
- Unpaid setups planted here
- The last situation the next chapter's first sentence must pick up, in one line
Rules: write nothing that is not in the text. Output the notes only.

[Manuscript]
[Chapter]

The 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

1
Fill in the variables
Enter your manuscript, characters or situation in the fields below. The example values are hints.
2
Check the assembled prompt
The prompt is assembled below with placeholders filled. Edit any rule to fit your work.
3
Copy it or run it
Copy it into the tool you already use, or run it in SparkLore for a short preview.
4
Revise 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

Stack these notes per chapter under a 'timeline' entry in your bible. Around chapter fifty they save the book.
'Knowledge' is the most important line. Continuity breaks the moment reader-only information leaks into a character.

Use it in the studio with your story bible

← Prompt library 이 라이브러리를 한국어로 보기