Use one skill for the complete editorial-to-video workflow while keeping the two phases independently invokable.
Select the intent
| User state or request | Intent to load |
|---|---|
| Raw recording/transcript; story is undecided; asks for themes, options, script, clips, or a shorter narrative | Read intents/storyline.md |
| A named script/version is already locked and the user asks to cut, render, assemble, or verify video | Read intents/video-edit.md |
| End-to-end request from a long recording to a finished short | Run storyline first; after the user unequivocally selects a named version and authorizes production, continue with video edit |
Existing edit-plan.json needs audit, rendering, or verification |
Read intents/video-edit.md |
Do not load both intent files when only one phase is requested. The shared handoff is approved-script.md: storyline creates it after approval; video edit treats it as immutable editorial input.
Shared invariants
- Recorded media is the authority. Transcripts and rough windows are search aids.
- Never invent, rewrite, or silently reconstruct spoken dialogue. Label authored cards or narration as editorial material.
- Apply privacy, legal, employer, client, and confidentiality exclusions across every active option and production handle.
- Preserve user agency. Storyline work presents genuinely distinct options and iterates; media production starts only after an unequivocal named selection.
- Rough transcript-derived windows are never frame-accurate. The editor must recover timestamped audio and align complete recorded phrase boundaries.
- If source audio contradicts the approved text, return the discrepancy for editorial review instead of substituting a nearby phrase.
- Completion requires the phase-specific evidence: a complete approved handoff for storyline, or a fully decoded and visually inspected final media file for video edit.
Resource map
- Story method: references/editorial-method.md
- Working options template: templates/editorial-options.md
- Approved handoff template: templates/approved-script.md
- Edit-plan contract: references/edit-plan.md
- JSON Schema: references/edit-plan.schema.json
- Deterministic renderer: scripts/render_video.py
Handoff boundary
approved-script.md contains source inventory, constraints, runtime, premise, ordered verbatim turns with rough source windows, omissions, visual notes, and approval evidence. It deliberately does not claim exact cut points. The video intent aligns each approved turn to timestamped source audio, writes a portable edit-plan.json, renders it with the bundled helper, and verifies the output end to end.