0
Chapter-by-chapter pacing map for a full manuscript
⁂auto-checked, 4 days oldAauraNovice
The prompt
I want a bird's-eye pacing diagnostic across my whole manuscript, not a scene-level edit. I'll give you a chapter-by-chapter summary (not full text) with approximate word counts and what happens in each.
Chapter summaries:
chapter_summaries_with_word_counts
Build me a pacing map:
1. Plot a rough tension/stakes curve across chapters (low/medium/high) based on what's described happening in each.
2. Identify any stretch of 3+ consecutive chapters at the same tension level with no escalation, that's likely a sagging middle.
3. Flag chapters whose word count seems mismatched to their apparent importance (a pivotal plot chapter that's unusually short, or a minor chapter that's unusually long).
4. Identify where major reveals/turns are placed proportionally through the book (e.g. 'reveal happens at 73% through') and tell me if that's early/late/on-target for the apparent genre.
5. Give me the single chapter you'd cut first if forced to cut one for pacing, and why, based only on the structural role it plays.
Work only from what I've given you, don't invent plot points.
Where it has been run
| Model | Version | People | Broke | Auto | Last |
|---|---|---|---|---|---|
| Claude | Haiku 4.5 | 0 | 0 | 1/1 | 4 days ago |
Example output
Tension curve: chapters 1-4 rise appropriately, but chapters 9-13 (five chapters) all sit at 'medium' with no escalation described, this is your sagging middle. Word count mismatch: chapter 14, which you describe as the midpoint reveal, is your shortest chapter at 1,800 words while chapter 6, a minor errand-running chapter, is your longest at 4,200, worth reversing that ratio. Major reveal placement: the antagonist's identity reveal lands at 81% through the book, quite late for the mystery-adjacent genre these summaries suggest, typically landing 65-75%. First cut recommendation: chapter 11, which by your summary repeats the 'protagonist argues with mentor' beat already covered in chapter 8 with no new information, purely structurally redundant.
0 comments
Sign in to comment or report what this prompt did for you.
Sign inNo comments yet. Run the prompt and report what you got.