Communitygithub.com

shot-list-schedule

Shows an agent how to plan, build, or cut "shot list schedule" so the concrete output is a beat sheet and shot list. The procedure moves through Shot List & Schedule, 1. Intake (always, before building), 2. Read the source. Use it when a new assignment calls for this craft.

What is shot-list-schedule?

shot-list-schedule is a Claude Code agent skill that shows an agent how to plan, build, or cut "shot list schedule" so the concrete output is a beat sheet and shot list. The procedure moves through Shot List & Schedule, 1. Intake (always, before building), 2. Read the source. Use it when a new assignment calls for this craft.

Works with~Claude Code~Codex CLI~Cursor
npx skills add https://github.com/thinkalim/ai-video-preproduction-skills/tree/HEAD/skills/shot-list-schedule

Ask in your favorite AI

Open a new chat with this agent skill pre-loaded.

Documentation

Shot List & Schedule

Deck in. A shoot day that actually fits out.

1. Intake (always, before building)

Ask in one short message, as a checklist. Never schedule until the required items are answered. Use what the deck already says and only ask for the gaps.

Required

  1. Day length, call to wrap, for each day (5, 8, 10, 12 hours, any length). Never assume.
  2. Call time for each day.
  3. Number of shoot days, and which scripts or scenes go on each, if the deck doesn't say.
  4. Locations: one or several per day, and which scenes shoot where.

Ask if relevant (skip what doesn't apply) 5. Date of each day. 6. Addresses and parking for each location. 7. Company moves: drive time between locations. 8. Talent: who is on which day, and hair and makeup needs. 9. Minors or animals on set. 10. Cameras: one camera or more (A, B). 11. Hard outs or fixed times: talent leaving early, location access windows, golden hour, a client call. 12. Crew and talent names, phones, producers, director. If none are given, write TBD. Never invent or add names. Never list the person running this skill in any crew, talent or producer field unless they name themselves for this shoot. Never carry over a name or phone number from an earlier project or a saved profile. Phone numbers only appear when the user types them in for this schedule.

If the user only gives a day length, build from the deck, use TBD for the rest, and list what's still open in the hand-off.

2. Read the source

  • Spec JSON from prepro-deck-builder: use it directly. Scenes, VO, text, talent, wardrobe and props are all there.
  • PDF: pdfplumber. Spreadsheet: openpyxl. Deck text in chat: use as is.
  • Per scene pull: number, INT/EXT and location, action, VO, on-screen text, characters, wardrobe, props.

3. Break scenes into shots

Read every frame and decide what coverage it needs on the first pass. The user edits from there.

Every scene gets a primary shot (201) and at least one coverage shot (201a) at another size or angle.

Add more shots when the frame has (each becomes 201b, 201c...):

  • More than one action ("she opens the drawer and slots the onesie in"): one shot per action.
  • A product feature, screen, label or detail called out: an INSERT or ECU.
  • An INSERT: line in the storyboard: its own shot, always.
  • Two or more people interacting: a two-shot plus singles or OTS on each.
  • A reaction or emotional beat: a CU on the face.
  • A reveal or pull-back ("close on the mat, pull back to reveal her"): start and end framings, or note the move.
  • A transition, match cut or split screen: both halves.
  • Movement through space (walks in, runs out, wheels down the hall): a wide to place it and a tracking or follow shot.
  • A hero product or end-card moment: a beauty shot plus a detail.
  • ASMR or sound-led moments (snap, click, pour): a tight shot that sees the sound.

Keep it lean. Don't add coverage a frame doesn't need. A simple product-only plate can stay at two rows.

Mark every added shot. In NOTES, after VO, TEXT and PROPS, add one line: SUGGESTED: why this shot (e.g. separate action, feature insert). The primary and first coverage shot are not marked. In the hand-off, give the count of suggested shots and say they can be cut or changed.

Format rules

  • Keep scene numbers: script 1 = 101, script 2 = 201.
  • Shot type uses abbreviations only: EWS WS MWS MS MCU CU ECU OTS POV OH INSERT. Combine with a slash (MS/MCU).
  • Description: first line slugline (INT. KITCHEN - DAY), action on the next.
  • Talent: character names only (Mom, Dad). Never actor names in the schedule. Hands-only: Name (hands). No people: Product only or None (plate).
  • Wardrobe: categories only (Casual, Business, Uniform + PPE). Itemized looks go in SET NOTES.
  • Notes, each on its own line, in this order: VO: "exact line" (mandatory, VO: None if silent), TEXT: ON-SCREEN COPY, PROPS: exact items and colorways. Every shot in a scene carries the same VO and TEXT. If the VO-to-scene mapping is unclear, ask.
  • Graphics-only scenes go in the GRAPHICS block, not the schedule.

4. Schedule the day

Group by location and setup, not script order. Shoot all of one setup before moving.

Default time per row (adjust for complexity, kids, animals, stunts, rigs):

RowMinutes
LOAD IN & SET UP60 to 90
SAFETY MEETING15
Simple shot or insert15 to 20
Talent shot with action or dialogue30 to 45
Product hero, beauty or rigged shot45 to 60
RESET: [WHAT'S CHANGING] (relight, new set)20 to 45
COMPANY MOVE30 to 60 plus drive time
LUNCH30
LOAD OUT45 to 60

Rules:

  • WRAP lands exactly at call plus day length. The builder warns if it doesn't.
  • Days over 6 hours get a 30-minute LUNCH starting within 6 hours of call. Days of 6 hours or less skip it.
  • If the shots don't fit, say which are at risk and ask before cutting anything.
  • Stagger talent calls. Allow up to 90 minutes for hair and makeup on heavier looks, less on lighter ones. Wrap times include a buffer.
  • Respect every hard out and fixed time from intake. Put fixed-time shots at their time and build around them.
  • Flag for the user, never decide: minors on set (hours and work rules vary by state and country), animals (add a wrangler), stunts, vehicles, water, permits for public locations.

5. Build

Write the schedule JSON, then run:

python scripts/build_schedule.py schedule.json outputs/<Project>_Schedule.xlsx

Shape (full example in references/example_schedule.json):

{
  "title": "Client - Project",
  "producers": ["TBD"], "director": "TBD",
  "days": [{
    "label": "Spot name or location", "date": "Mon, Mar 2", "call": "7:00 AM", "length_hours": 10,
    "locations": [{"name": "Location 1", "address": "", "city": "", "parking": ""}],
    "rows": [
      {"type": "logistics", "label": "LOAD IN & SET UP", "minutes": 60},
      {"type": "shot", "shot": "101", "size": "WS", "camera": "A", "desc": "INT. ROOM - DAY\nAction.",
       "talent": "Name", "wardrobe": "Casual", "location": "Room", "notes": "VO: None", "minutes": 30},
      {"type": "logistics", "label": "WRAP", "minutes": 0}
    ],
    "graphics": [{"shot": "110", "desc": "End card", "notes": "VO: None\nTEXT: LOGO"}],
    "crew": [{"role": "Director", "name": "TBD", "phone": "", "call": "", "wrap": ""}],
    "talent": [{"role": "Character", "name": "TBD", "call": "", "wrap": "", "notes": ""}]
  }],
  "set_notes": {
    "deliverable": ["30s Video (x1)"], "distribution": "", "client": "", "note": "",
    "product": {"About": "", "Key Features": [""], "Mood / Tone": ""},
    "set_notes": {"Wardrobe": [""], "Props": [""], "Open Items": [""]}
  }
}

The builder owns the look: Avenir, hidden gridlines, color-coded logistics rows (load in green, safety peach, resets and moves blue, lunch yellow, load out and wrap red), live start-time formulas so editing any duration reflows the day, and auto row heights.

Review pass (always, before presenting)

Every answer runs twice. The user never sees the first draft.

  1. Draft the full answer.
  2. Review it the way a demanding creative director and producer would, against the checklist below and every rule in this skill. Read the copy as if hearing it in a client meeting. Mark every miss.
  3. Fix every miss, then present only the revised version.
  4. End with one line: Review pass: <what changed>, or Review pass: no changes needed.

This applies to every step that produces something: research, options, copy, specs and files. For a file, build it, open or render it, check it, then fix and rebuild before handing it over.

Checklist

  • Builder warnings at zero, or each one explained to the user.
  • Every scene has a primary and a coverage shot. Every shot carries its VO. Suggested shots are marked.
  • Durations fit the action. Lunch, wrap and every hard out are respected. At-risk shots are flagged, never cut.
  • Talent listed by character only. No invented names, no names or phones carried over from past projects, and the user is never listed unless they named themselves for this shoot. No em dashes.

6. Check, then hand off

  • Builder prints warnings. Fix every one or tell the user why it stands.
  • Every scene has at least two shots. Every shot has a VO line. No actor names in the schedule.
  • No names the user didn't give. No em dashes.
  • Hand off in 3 lines: days, shot count and how many were suggested, then flags (at-risk shots, minors, animals, permits, open items).

Individual skills in this repo

This repo contains 2 individual skills — each has its own dedicated page.

Related Skills