Promise and payoff: find the pairs that thread a multi-day film
An agent prompt that reads several days of transcripts and pairs every promise ('tomorrow we'll buy the boat') with the moment it is kept or broken, so the film has a thread, not a sequence of days.
Below are the transcripts of {N} days of footage, in shooting order, each sentence tagged with day, clip and time. Find every PROMISE: a sentence about something that will happen later (a plan, a wish, a bet, a 'tomorrow', a 'we'll see', a 'never again'). For each, search the later days for the PAYOFF: the moment it happens, fails, or is mentioned again. Output a table: Promise (day, clip, time, quote) | Payoff (day, clip, time, quote, or 'none found') | Type (kept / broken / forgotten) | Gap in days | Keep both? (yes if the payoff is visible on camera or said clearly). Then propose the thread: the 3-5 pairs that would carry the whole film, in the order they should appear, with one sentence on why each one matters to someone who was not there. Mark any promise without a payoff that is still worth keeping as an open question for the ending. Transcripts: {paste day transcripts}
In Claude Code, paste the prompt as a message, or run /video-edit which does this end to end.
Steps
- Transcribe all days first and fix names with a glossary; a promise about 'Mehmet' and a payoff about 'Mohammed' will not be paired.
- Run the prompt over all days at once, not per day. The pairs cross days by definition.
- Keep both halves of every chosen pair in the cut, in order. A payoff whose promise was cut is a random event; a promise whose payoff was cut is a loose end the viewer notices at the credits.
Tips
- Broken promises make better threads than kept ones. 'We'll catch the 7 am ferry' followed by the midnight ferry is the film.
- A long trip film is cut from the finished day films; find the pairs before cutting the days, so each day keeps its half.
| works with | Claude Code: Runs as a skill or a prompt in the terminal; can read your files and write the result. · Claude: Paste into claude.ai or the Claude app. |
| skill | npx skills add fortunto2/solo-factory/video-edit · source |
| cost | Free. No API, no key. |
| status | Unverified: written from the technique, not yet run end to end by us. |
| license | CC BY 4.0 for the text here; skills are MIT. |
| updated | 2026-11-01 |
| for agents | promise-payoff-pairs-multi-day-film.md |
Related
The day as one text file: an agent reads the speech and proposes the story
The step before any timeline: the day's speech in shooting order, numbered by clip and sentence, read by an agent like a scriptwriter. It proposes story, scenes, hook and cutaways; you argue in text.
Scenes, not best phrases: keep the lead-in, the talk and the reaction
Why a reel of good lines confuses everyone who was not there, and the checklist for keeping a scene whole: the lead-in, the talk, the reaction, with filler trimmed only at the ends.
Read the film as text before rendering: the last check that costs nothing
The cut, printed as its lines in order, read by someone who never saw the raw footage. Catches the question whose answer was cut, the name said before the person, the 'this' that points at nothing.
The cutaway rule: what is said, same place and time, never over moving lips
Three constraints for every cutaway in a talking film, and the agent prompt that applies them to a transcript. Kills what viewers read as broken: a picture from elsewhere, a face out of sync.
Generate a 10-clip b-roll pack for a talking-head video
One agent prompt that reads your transcript and writes ten generation prompts for cutaways that show what is being said, each tagged with the sentence it covers.
Beat-sync cutting: cut on the beat, not on every beat
A rule and an agent prompt for cutting to music from a list of beat timestamps: cuts land on beats, phrases get room to breathe, and the best shot is held through the hook.