The practical guide
From a good idea to a clear handoff.
Know what to ask, where to click, and what to check before your editor gets the draft.
Start with the public overview. Sign in for detailed, step-by-step guides.
Start here
Your first editor-ready draft
Follow the path from a rough idea to a script, suggested footage and a link your editor can use.
Read guideWhat ReadyToEdit reads
What it takes from GitHub, Google Drive, uploads and social accounts, the file limits, and what it does not connect to.
Read guideUse ReadyToEdit from your AI agent
Connect Claude or another MCP client once, then have it send your notes, start a draft and hand you the editor link.
Read guideShape the draft
Set your goals, style and audience
Say what your project is about, who it is for, what it should achieve and how it should sound. Add blocks of your own, give one piece its own Audience, Goals or Style, and see which actions receive which instructions.
Read guideWhat the assistant reads
Understand what wins when instructions disagree, and read exactly what two actions receive from the same project.
Read guideWhat it learns from your edits
Which corrections it notices, when they carry into later drafts, and how to correct what it learned.
Read guideRead an opening closely
What a close read of an opening reports, what it compares against, and why it gives no score.
Read guideTurn an idea into a draft with clips
Create a complete draft, review beat-by-beat footage suggestions, and handle gaps without inventing support.
Read guideWork with your editor
Keep and export your conversation
Copy a useful message or download the whole exchange with your words separated from the assistant’s.
Read guideShare a clear editor handoff
Give your editor the script, beat placements, playable clips and original file links in one read-only page.
Read guide