dp-review-final-report

Validate manuscript consistency against world settings, character data, outlines, and timelines.

66|5|Updated Mar 29, 2026
One-click install
npx skills add https://github.com/skyfiredao/dreampowers --skill dp-review-final-report
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dp-review-final-report
Source: https://github.com/skyfiredao/dreampowers/tree/main/skills/dp-review-final-report
Command: npx skills add https://github.com/skyfiredao/dreampowers --skill dp-review-final-report

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides a post-draft, global consistency validation by comparing all final chapters against the world settings, character cards, outlines, and timelines to uncover contradictions and ensure coherence.

Core Features & Use Cases

  • Global consistency validation across chapters, world-building rules, and character relationships.
  • Foreshadowing and timeline checks to ensure setup/payoff alignment throughout the manuscript.
  • Structured final report that highlights unresolved items, deviations from the outline, and recommended follow-ups for writers.

Quick Start

Run the final report once all chapters are finalized to generate a comprehensive, cross-document consistency assessment.

Frequently Asked Questions about dp-review-final-report

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I perform a full-book consistency check after drafting my manuscript?

Perform a full-book consistency check by validating final chapters against world settings, character data, outlines, and timelines to uncover contradictions, verify global coherence, and flag unresolved foreshadowing.

What is end-to-end manuscript validation and how does it work?

End-to-end manuscript validation compares finalized chapters against worldbuilding rules and character cards to detect deviations. It cross-references timeline events and outline structures to ensure global narrative coherence across the entire book.

When do I need to run a final report for foreshadowing and timeline checks?

Run a final report for foreshadowing and timeline checks once all manuscript chapters are finalized. This post-draft stage validates setup and payoff alignment, ensuring unresolved narrative threads are explicitly flagged before release.

Can I use this consistency check on an incomplete manuscript with missing chapters?

This consistency check applies to post-draft review workflows requiring all finalized chapters. Running it on incomplete manuscripts limits global coherence validation, preventing accurate cross-referencing of world settings, character data, and timelines.

What is the best way to track unresolved foreshadowing across a completed book?

Track unresolved foreshadowing by running a structured final report that cross-references chapter content against outlines and timelines. This generates explicit risk flags for setup-payoff misalignments and recommended follow-ups for writers.

Where does the generated final report output get saved?

The generated final report outputs to docs/dreampowers/release/final_report.md. It loads supporting materials from docs/dreampowers to validate manuscript consistency and highlights unresolved items, outline deviations, and recommended follow-ups.