Skip to content
Wonderthrough Request early access

Advanced Analysis

Wonderthrough includes deeper AI analysis tools that work above the level of a single prompt or one short chat exchange. These tools are best when you want structured feedback across a scene, a character, an arc, or an entire book.

What counts as advanced analysis?

Section titled “What counts as advanced analysis?”

Advanced analysis is the set of tools that look at a larger slice of your project and return organized findings rather than a quick conversational answer.

Examples include:

  • Scene Analysis for scene-level craft and extraction signals
  • Profile Enrichment for building out characters and locations from what the manuscript already implies
  • Trajectory for a character’s internal movement across the book
  • Arc Coverage for how well an arc is supported by its linked scenes
  • Arc Discovery for surfacing candidate arcs from the manuscript
  • Book Synthesis for higher-level manuscript patterns and cross-book observations

When should I use advanced analysis instead of chat?

Section titled “When should I use advanced analysis instead of chat?”

Use advanced analysis when you want structured findings grounded in project data. Use chat when you want back-and-forth thinking, coaching, or brainstorming.

Advanced analysis is usually the better choice when you want:

  • a repeatable pass over existing material
  • findings you can review and accept selectively
  • a clearer picture of patterns across scenes, characters, arcs, or the whole book

Chat is usually better when you are still framing the question or want help deciding what to try next.

Which analysis tool should I use?

Section titled “Which analysis tool should I use?”

Use Scene Analysis when:

Section titled “Use Scene Analysis when:”
  • you want to inspect a specific scene
  • you want craft, continuity, or extraction findings tied to one moment
  • you are revising the scene itself

Use Profile Enrichment when:

Section titled “Use Profile Enrichment when:”
  • the manuscript already implies details about a character or location
  • you want Wonderthrough to help populate a profile from what is already there
  • you want a stronger project reference page without filling every field manually

Use Trajectory when:

Section titled “Use Trajectory when:”
  • you want to understand a character’s internal movement across the book
  • you are testing whether the arc has enough progression or clarity
  • you need a higher-level character read than scene-by-scene notes can give you

Use Arc Coverage when:

Section titled “Use Arc Coverage when:”
  • an arc already exists and has linked scenes
  • you want to see whether the manuscript is actually supporting that arc
  • you need to spot weak, missing, or misaligned beat coverage

Use Arc Discovery when:

Section titled “Use Arc Discovery when:”
  • you suspect the manuscript contains arcs that have not been named clearly yet
  • you want help surfacing candidate arcs from existing scenes
  • you are moving from exploratory drafting into more explicit structure

Use Book Synthesis when:

Section titled “Use Book Synthesis when:”
  • you want a broader read on the manuscript as a whole
  • you need cross-scene or cross-character patterns
  • you want to step back and see what the book is doing overall

What Book Synthesis shows you

Section titled “What Book Synthesis shows you”

Book Synthesis is the widest read of all — it looks at the whole manuscript at once and reports on what the book is doing overall. Its findings group into a few kinds:

  • The book’s core — its premise, central conflict, dominant themes, and who it reads as centering on.
  • Shape and pacing — where the midpoint seems to fall, how tension rises and eases across the book (pacing zones), and whether the ending pays off what the opening set up.
  • Gaps and mismatches — structural gaps where the spine is thin, places where the stakes seem to rise but nothing underneath is actually moving (hollow escalation), and whether your arcs and your characters’ inner journeys line up.
  • Loose ends — threads the book opens but never resolves.

Because it draws on everything at once, Book Synthesis is most useful once the manuscript has real material — run too early, it has little to work with. As with the other tools, treat its findings as a clearer view of the book, not a verdict.

What makes these tools work better?

Section titled “What makes these tools work better?”

These tools get stronger as the project gets more real.

In practice, results improve when:

  • scenes are actually drafted rather than placeholder-thin
  • important characters and locations are named consistently
  • arcs and links are at least partly defined where relevant
  • the manuscript contains enough material for the tool’s scope

If the project is still mostly empty, the tool may still run, but the result will naturally be thinner.

How should I read the results?

Section titled “How should I read the results?”

Treat the results as informed findings, not automatic truth.

The strongest workflow is usually:

  1. review the findings
  2. accept what is clearly useful
  3. dismiss what is not
  4. use the result to guide revision, not to replace judgment

Wonderthrough is helping you see the project more clearly. It is not deciding the manuscript for you.

When should I not use advanced analysis yet?

Section titled “When should I not use advanced analysis yet?”

Do not reach for a deep analysis tool just because it exists. It is often better to wait until the project has enough material for the question to be meaningful.

You may want to wait if:

  • the scene is only a fragment
  • the book does not yet have enough scenes for higher-level patterns
  • you are still deciding basic world or story premises
  • a quick chat would answer the question faster
Section titled “Related help”