story-critic

To check for plot holes and character inconsistency, review the drafted chapter against its chapter plan, story bible, and progress log. This developmental editing process identifies worldbuilding contradictions and pacing weaknesses, producing a structured review file with prioritized revision recommendations.

Developmental editing for fiction writing involves evaluating a chapter against its plan and canonical story documentation. This process checks plot consistency, character voice, and timeline logic, generating an editorial output that highlights strengths, prioritizes issues, and marks acceptance criteria as pass or revision.

Yes, you can use chapter plans and PRD-style acceptance criteria to review narrative quality. By comparing the drafted text against predefined chapter requirements and story bible rules, you can verify unmet story threads, pacing problems, and show-versus-tell issues before moving to the revision step.

Continuity checking does not work effectively without a story bible and progress tracking. The review process requires reading canonical story documentation, chapter plans, and progress notes to verify plot consistency, character voice, and world rules across the broader narrative before generating a pass or revision status.

A story review shows pacing weaknesses and unmet chapter requirements when the drafted text deviates from the chapter plan or story bible. The review process reads the target chapter, its plan, and progress notes to identify these contradictions, writing a structured editorial output with prioritized revision actions.

Automated story review for long-form fiction writing is limited by its dependency on existing documentation. It requires a pre-established story bible, chapter plans, and progress tracking to identify plot holes and character inconsistency, meaning it cannot review narrative quality or worldbuilding contradictions without these canonical inputs.