90day-production-docs

name

90day-production-docs

description

Generates production paperwork from existing story materials — post-handoff packages, production kick-off sheets, and story transfer documents. Uses established templates and populates them from beat sheets, scene breakdowns, and cast information. Use when creating handoff docs, kick-off sheets, story transfers, or any production documentation that follows a standard template. Triggers on "handoff", "kick-off sheet", "story transfer", "production docs", "wrap docs", "post-production package", "prep the paperwork", "get this ready for handoff", "transfer document", "kick off", or when transitioning between production phases.

90 Day Production Docs

Template-driven document generator for the production paperwork that bridges creative story work and field execution. These documents are the handshake between story producers, field producers, and post-production — each one structured to give the next person exactly what they need, nothing more.

When to Use This Skill

• Pre-Production: Kick-off sheets when a new couple enters production
• Mid-Production: Story transfers when handing work between sessions or producers
• Post-Production: Handoff packages when field work wraps and post takes over
• Session Continuity: Story transfers to maintain context across Claude sessions

The Three Document Types

Document 1: Production Kick-Off Sheet

Purpose: Everything a field producer needs to start shooting. Cast info, locations, scenes to capture, timeline, logistics.

When to Generate: New couple entering production, or when a new segment/shoot begins.

Source Material Needed:

• Completed beat sheet or scene breakdown (Phase 2+ from story-development)
• Cast contact information
• Location list
• Production timeline/schedule

Template Location: Read Production Kick-Off Sheet Template.md from the project knowledge base.

How to Populate:

1. Story Summary — Pull from the Phase 1 story foundation. 2-3 sentences: core conflict, current situation, where story is heading. Write in TLC voice (present tense, active).

2. Cast Section — Main couple with full contact details + ancillary characters with their story function. Only include ancillary characters who appear in approved scenes.

3. Locations — Extracted from beat sheet scene headers. Group by segment. Include any access/permission notes.

4. Key Activities/Scenes — One-line per scene from the Phase 2 scene lines. Checkbox format for field tracking.

5. Timeline — Key dates and milestones. Include visa deadlines, events, or external pressures that affect story.

6. Production Notes — Anything that affects how the shoot runs: scheduling constraints, technical requirements, cast quirks, equipment needs.

7. Safety/Logistics — Health considerations, legal/visa issues, location safety, travel logistics.

8. Immediate Needs — Action items that must happen before cameras roll.

Voice Rules for Kick-Off Sheets:

• Direct and practical — field producers need clarity, not storytelling
• Bullet points are appropriate here (this is logistics, not narrative)
• Include exact addresses, phone numbers, dates
• Flag anything time-sensitive or requiring approval

---

Document 2: Post-Production Handoff

Purpose: Bridges what was planned (beat sheet) with what was captured (field reality). Tells post-production what they have to work with, what's missing, and how to assemble it.

When to Generate: After field production wraps on a couple's segment.

Source Material Needed:

• Original beat sheet / scene breakdown
• Shoot notes or field report (what actually happened)
• Interview completion status
• Any production issues or changes from plan

Template Location: Read Post_Handoff_Template.md from the project knowledge base.

How to Populate:

1. Part 1: The Planned Story — Paste the original story foundation and scene architecture. This is the reference point.

2. Part 2: What Actually Happened — Scene-by-scene comparison: PLANNED vs. GOT. Status checkbox for each: As planned / Got differently / Didn't get / Got better. Post notes for each scene explaining deviations.

3. Part 3: Gap Analysis — Critical beats status table. Story holes with solve strategies (what's missing, why, how to fix — usually through INTV or pickups). Unexpected gifts section — moments better than planned.

4. Part 4: Interview Coverage — What INTV sessions were completed. Which topics are covered. What pickups are still needed (specific questions/topics).

5. Part 5: Assembly Guidance — Recommended structure (Open → Build → Turn → Land). "Protect These Moments" — authentic gold to preserve. "Handle Carefully" — issues, sensitivities, technical problems.

6. Part 6: The Bottom Line — Binary assessment: Can we tell this story? Yes / Yes with work / Needs intervention. One-line status summary.

Voice Rules for Handoffs:

• Honest assessment — don't sugarcoat gaps
• Specific about what's missing and how to solve it
• "Protect These Moments" section should read like a field producer who's genuinely excited about what they captured
• Bottom line must be clear and actionable

---

Document 3: Story Transfer

Purpose: Continuity document for passing story work between Claude sessions or between producers. Everything needed to pick up exactly where the last session left off.

When to Generate: End of any working session where story development is in progress. Or when another producer is picking up the work.

Source Material Needed:

• Current state of story development (which phase)
• All completed work products
• Context and background on the couple
• What's next (task request for the receiving session/producer)

Template Location: Read story_transfer_template.md from the project knowledge base.

How to Populate:

1. Story Identification — Show, couple, episode, current phase, last updated, session type. Quick header for instant context.

2. Story Foundation — Paste the Phase 1 one-line story summary.

3. Scene Breakdown — Paste Phase 2 scene lines with Therefore/But/Because connections.

4. Current Work State — Checklist of completed phases. Paste in-progress work. Paste most recent complete section.

5. Context & Background — Couple summary, key conflicts (primary/secondary/external), timeline/urgency.

6. Cast & Locations — Main and ancillary cast with story functions. Key locations per scene.

7. Production Notes — Special considerations, red flags, story direction notes.

8. Task Request — Specific instruction for next session. Output format needed (checkboxes).

9. Creative Direction — Tone/style reminders, story priorities for this couple, fresh angles to explore.

Voice Rules for Transfers:

• Context-rich but not bloated — the receiving session needs to get up to speed fast
• Paste actual work product, don't summarize it
• Task request must be specific and actionable ("Expand Scene 2 beats into full production-ready text" not "continue working on the story")

---

Document Generation Process

Step 1: Identify Document Type

Based on where you are in production:

• Starting a shoot → Kick-Off Sheet
• Wrapping a shoot → Post-Handoff
• Switching sessions/producers → Story Transfer

Step 2: Gather Source Material

Read the relevant templates from the knowledge base. Identify what information is available and what's missing. If critical fields are empty, flag them as [NEEDS INFO] rather than guessing.

Step 3: Populate Template

Fill every section. Use TLC voice for narrative sections (story summaries, assembly guidance). Use direct/practical voice for logistics sections (cast info, locations, timelines).

Step 4: Voice Gate Check

Before delivering, run through a quick voice check:

• Narrative sections in present tense, active voice?
• No AI slop patterns? (no "furthermore", no "it becomes clear")
• Logistics sections are clear and specific?
• Nothing left as placeholder text from template?
• All [bracketed instructions] replaced with actual content?

Step 5: Deliver as .docx

Production docs are typically delivered as .docx files for distribution to the team. Use the docx skill for formatting if available.

Integration with Pipeline

• Input from 90day-story-development: Beat sheets and scene breakdowns feed kick-off sheets and transfers
• Input from 90day-cast-logistics: Cast profiles feed the cast sections of all three documents
• Input from 90day-production-readiness: Rubric scores inform the handoff's assessment sections
• Input from 90day-voice-gate: Cleaned narrative sections for story summaries and assembly guidance
• Standalone use: Any document can be generated independently when you have the source material