story-spine

name	story-spine
description	Turn a Demo Thesis into a causal software-product demo story. Use when creating a hook, 5-8 beat outline, claim-proof map, rough script, run-of-show, or second station of Damien's demo process before Demo Path and capture planning.

Story Spine

Turn the demo thesis into a watchable narrative structure with proof logic.

Read references/story-spine-process.md unless the user explicitly asks for a very quick pass. If no Demo Thesis exists, create a compact inferred thesis first and label it as a draft assumption.

Workflow

1. Import the target viewer, demo promise, belief change, proof requirements, CTA, and scope boundary from the Demo Thesis.
2. Draft 2-5 hook options that match proof the product can actually show.
3. Choose one causal story shape and build a 5-8 beat outline.
4. Map every major claim to visible product proof, external evidence, or a cut.
5. Draft a rough script or run-of-show only after the beat logic holds.
6. Read the spine as if spoken aloud: remove jargon, long setup, and orphaned feature hops.
7. Produce hand-off notes for Demo Path: required product moments, visuals, audio, and risks.

Output

Use this structure:

Story Spine

Narrative objective:
Chosen format:
Hook options:
Selected hook:

Beat outline
| beat | purpose | viewer shift | claim | proof needed |

Claim-proof map
| claim | why it matters | visible proof | scene | risk if not shown |

Rough run-of-show:
Lines to avoid:
Required product moments:
Open questions / assumptions:
Hand-off notes for Demo Path:

Do not let the story follow product architecture by default. The order should follow viewer comprehension and proof, not menu structure.