video-plan

video-plan

You are writing the two documents a video gets approved on, and nothing else. No capture, no cutting, no rendering — that is the demo-video skill, and it refuses to start without these.

PLAN.md    the SHAPE — purpose, audience, beats, targets, spotlights, privacy, out of scope
SCRIPT.md  the WORDS — card copy, typed strings, required AI answers, the spoken track

Why they are separate documents: a plan can be right while the copy is wrong, and copy is the thing reviewers actually react to. A stakeholder can approve words; they cannot approve a beat table.

Why they come first: the arc is what changes under review, and every beat captured against an unagreed arc gets re-captured. A sentence that changes after the shoot can cost the whole flow, because patching one beat into an existing cut is usually not available.

Usually, not always — and the condition is worth knowing, because it decides how expensive a late change is:

A single beat can be re-shot only when the scene shares no state with its neighbours, and the source renders stably between runs, and no audio anchor crosses the scene boundary.

On a demo of your own app the first two are typically violated: time-of-day greetings and relative timestamps drift between runs, so a patched beat is visibly discontinuous with the ones around it. On a self-contained section of a third-party website they typically hold. The third condition is the one that comes back later — the moment narration is added, a re-shot beat of a different length moves every following audio anchor, and a pipeline that could re-shoot freely while it was silent can no longer do it.

Reading the app in order to write the plan is fine and expected. Recording it is not. The same holds for a website you do not own — read it, do not film it yet, and do not click anything that writes.

Need	Read
the standard two-part feature-guide format (the default ask — read FIRST if it's a guide)	references/guide-format.md
the subject is a WEBSITE, not an app you sign into (the tour arc, and the permission questions that belong in the plan)	references/site-tour-format.md
is there a concept of the application? (the reusable half — what the product is for, its flows, the words on screen)	references/application-concept.md
the exact shape of both documents, with a fill-in template	references/plan-and-script.md
caption card copy — what a headline may and may not do	references/copy-rules.md
the spoken track — grammar traps, audience fit, tone	references/spoken-track.md

---