ppt-story-refine

To fix a presentation storyboard with illogical section order and buried conclusions, you refine the narrative structure by reordering pages, redefining sections, and inserting transition or summary pages. This restores the logical flow and corrects pacing without redoing research or design controls.

Yes, you can rebalance page allocation without losing source references. The storyboard refinement process merges, splits, or creates pages while strictly preserving source_claim_ids and source_evidence_ids integrity, updating page_number and total_pages sequencing, and maintaining existing page_id values.

The best way to move a core conclusion to the first third of a product update deck is through storyline repair. This structural edit reorders the narrative sequence to restore audience-focused pacing, rebalances pages according to task-pack guidelines, and generates a concise change summary for handoff.

Yes, PPT story refinement reevaluates payload budget and lists downstream artifacts. It reassesses the payload_budget per content_density_profile and reports downstream artifacts requiring updates, including HTML pages, style variants, and asset plans affected by the structural changes.

You need to refine PPT storyboard narrative structure when a presentation's facts and assets are ready but the storytelling is disorganized. This includes scenarios where ppt-review flags issues such as delayed conclusions, ambiguous narrative roles, or imbalanced page distribution across sections.