Storyline
# ppt_deck / storyline
## Goal
Turn the complete accepted source, speaker identity, audience, and delivery goal into a source-grounded claim spine and narrative journey.
## Good Work
- Read `source_materials_full_text` before deciding the story. Titles, excerpts, fact summaries, and page budgets are not substitutes for source judgment.
- Preserve exact named speaker identity and public naming when supplied.
- For manuscript/paper reporting, organize the story around each research question, method, key numeric result, conclusion, and limitation; do not invent clinical deployment or promotional value.
- When requested, extract a manuscript evidence table from the full source so downstream outline/blueprint stages can retain the actual numbers and boundaries.
- Define audience, style, hook, journey, resolution, and a stable `claim_spine_lock` with source refs, first-use naming, proof/resolution roles, and forbidden drift.
- Let later outline, capacity, or visual discoveries route back to the smallest affected story decision. Freeze only explicitly approved story judgments.
## Handoff
Return the storyline object required by the attached output contract. It must be strong enough for `detailed_outline` without prescribing page count, sample slide ids, or layout geometry.when to use it
Community prompt sourced from the open-source GitHub repo gaofeng21cn/redcube-ai (Apache-2.0). A "Storyline" style prompt — adapt the placeholders and specifics to your task. Imported as-is and not independently retested here, so check the output before relying on it.
tags
roleplaycommunitygeneral
source
gaofeng21cn/redcube-ai · Apache-2.0