Reconstructs the complete chronological timeline of a manuscript and stress-tests it for
internal consistency. AI-generated novels are especially prone to temporal errors because
models lose track of elapsed time across long generation sessions.

## Key Points

- User says "check my timeline", "find time inconsistencies", "build a timeline from my book"
- User suspects impossible travel times or aging errors
- User has a complex narrative with flashbacks, time jumps, or multiple parallel threads
- As a deeper dive following timeline flags from the Novel Audit's Module 3
- **The manuscript** — full text
- **World-building notes** (optional) — travel times, geography, technology level
- **Outline with dates** (optional) — intended timeline
- Dates ("March 15th", "2024", "the summer of 1989")
- Clock times ("at noon", "3 AM", "by sunset")
- Named days ("Monday", "on Wednesday")
- Seasons and weather as time indicators
- "Three days later", "the following week", "a month had passed"

Timeline Continuity Checker Skill

Reconstructs the complete chronological timeline of a manuscript and stress-tests it for internal consistency. AI-generated novels are especially prone to temporal errors because models lose track of elapsed time across long generation sessions.

When to Use This Skill

• User says "check my timeline", "find time inconsistencies", "build a timeline from my book"
• User suspects impossible travel times or aging errors
• User has a complex narrative with flashbacks, time jumps, or multiple parallel threads
• As a deeper dive following timeline flags from the Novel Audit's Module 3

Input Requirements

• The manuscript — full text
• World-building notes (optional) — travel times, geography, technology level
• Outline with dates (optional) — intended timeline

Timeline Construction Process

Step 1 — Time Reference Extraction

Scan the manuscript for every temporal marker:

Explicit markers:

• Dates ("March 15th", "2024", "the summer of 1989")
• Clock times ("at noon", "3 AM", "by sunset")
• Named days ("Monday", "on Wednesday")
• Seasons and weather as time indicators

Relative markers:

• "Three days later", "the following week", "a month had passed"
• "Yesterday", "last night", "the previous summer"
• "After the funeral", "before the wedding" (event-relative)

Implied markers:

• Meal times suggesting time of day
• Light/dark descriptions indicating time
• Character age statements
• Pregnancy/growth/seasonal progression

Step 2 — Event Sequencing

1. Place every scene on a linear timeline using extracted markers.
2. Where markers are ambiguous, assign a range (e.g., "sometime in Week 2").
3. Track parallel threads separately, then synchronize at intersection points.
4. For non-linear narratives (flashbacks, frame stories), maintain both story-order and chronological-order timelines.

Step 3 — Consistency Testing

Run these checks against the constructed timeline:

Temporal Impossibilities

• Events that happen before their stated causes
• A character in two locations at the same time with no explanation
• "Three days later" followed by references to events "yesterday" that should be four days ago

Travel Time Violations

• Characters traveling between locations faster than physically possible
• If the world has established transportation (horses, cars, spaceships), verify travel durations match the technology level
• Walking speed: ~3 mph. Horseback: ~25 mph sustained. Car: varies. Flag anything suspicious.

Aging Inconsistencies

• A character stated as 30 in chapter 2 and 28 in chapter 15
• Children who grow too fast or not at all over stated time periods
• "Ten years ago" flashbacks that contradict character ages

Duration Problems

• Events that take longer than physically possible within their stated timeframe
• Conversations that last hours of story-time but are only a few lines
• Battles or chases that span an impossibly long or short period

Seasonal and Environmental Conflicts

• Snow in a scene set in July (northern hemisphere) without explanation
• Crops harvested in the wrong season
• Daylight at hours when it should be dark for the setting's latitude

Step 4 — Conflict Severity Rating

Severity	Definition
CRITICAL	The timeline is logically impossible — reader will notice
MAJOR	Timeline requires an implausible stretch — attentive reader will question
MINOR	Slightly off but most readers won't catch it
NOTE	Not an error, but a potential source of reader confusion

Output Format

# Timeline Continuity Report
**Title**: [Novel title]
**Date**: [Today]
**Timeline span**: [start date/period] to [end date/period]
**Time references found**: [N]
**Conflicts found**: [N]

## Reconstructed Timeline

| Story Order | Chrono Order | Chapter | Event | Time Marker | Elapsed Since Start |
|-------------|-------------|---------|-------|-------------|-------------------|
| 1 | 1 | Ch. 1 | [event] | "March 15" | Day 1 |
| 2 | 3 | Ch. 2 | [event] | "a week later" | Day 8 |
| ... | ... | ... | ... | ... | ... |

## Parallel Thread Sync Points

| Thread A Event | Thread B Event | Sync Marker | Consistent? |
|---------------|---------------|-------------|-------------|
| ... | ... | ... | Yes/No |

## Conflicts Found

### [Conflict ID] — [Severity]
- **Location**: Chapter X vs. Chapter Y
- **The problem**: [description]
- **Evidence**: "[quote from Ch. X]" vs. "[quote from Ch. Y]"
- **Suggested fix**: [how to resolve]

[Repeat for each conflict]

## Timeline Gaps

[Periods where no time markers exist and elapsed time is uncertain]

## Recommendations
[Prioritized list of fixes]

Handling Non-Linear Narratives

For stories with flashbacks, dual timelines, or time travel:

• Construct each timeline strand independently first.
• Map connection points between strands.
• Verify internal consistency within each strand before checking cross-strand consistency.
• For time travel: note the rules established in the text and verify they are followed consistently. Paradoxes are only errors if they violate the story's own rules.

Anti-Patterns

Demanding precision where the text is vague. If the manuscript says "a few days later," that is 2-5 days. Do not flag it as an error unless surrounding evidence makes every interpretation within that range impossible.

Ignoring genre conventions. In fantasy, seasons may not work like Earth's. In sci-fi, travel times depend on fictional technology. Verify against the story's established rules, not real world assumptions — unless the story is set in the real world.

Missing implied time references. "She ate breakfast" tells you it's morning. "The stars came out" tells you it's evening. These soft references matter when hard references are absent.

Treating the outline timeline as authoritative over the manuscript. The manuscript is the text that will be published. If the outline says Day 5 but the manuscript says Day 3, the conflict is in the manuscript's internal logic, not in outline deviation (that's a different skill's job).

Overwhelming the author with minor notes. If you find 50 minor timing ambiguities and 3 critical impossibilities, lead with the 3 critical items. The minor notes go in an appendix.