ChatGPT for Screenwriting
Most writers open a fresh chat, type "help me with my script," and get mush back. The difference between mush and a real writing-room partner is setup. Here's the working configuration I actually use — and the five prompt patterns that earn their keep.
Everything I said in the first two chapters about AI's limits stays true. But limits and uselessness are different things, and used with a little discipline, ChatGPT — or Claude, everything here applies to both — becomes something genuinely rare for a writer working alone: a development partner that never gets tired of your script. Not a writer. A partner. The setup below is how you keep it on the right side of that line.
The first rule is organizational, and it's the one everyone skips: one project per script. Both ChatGPT and Claude let you group conversations into a project with shared files and instructions. Make one for each screenplay. Drop in your logline, your character bios, your outline, and your latest pages as they exist. Now every conversation starts already knowing your story — you're not re-explaining your protagonist for the fortieth time, and the feedback you get is about your script instead of scripts in general. This one habit is the difference between a writing-room and a fortune-teller's booth.
The five prompt patterns that actually work
Once the room is set up, what you say in it matters more than any tool choice. After a couple of years of doing this on real projects, almost everything useful I do reduces to five patterns:
- 1. Ask for questions, not answers. "Ask me ten hard questions about this outline that a skeptical producer would ask." The questions expose your soft spots; answering them is writing.
- 2. Ask for ten options, never one. One suggestion invites you to accept it. Ten force you to judge — and your taste, choosing and rejecting, is doing the authorship.
- 3. Ask it to argue against your choice. "I'm killing this character in act two. Make the strongest case that I shouldn't." If the case is weak, proceed with confidence. If it's strong, you just saved a rewrite.
- 4. Ask it to interrogate your scene, not write one. Paste your pages and ask: where does the tension drop, who's driving, what does each character want and hide? Notes on your writing, not replacement writing.
- 5. Ask for the reader's experience. "Describe what a first-time reader feels page by page through this sequence." It's a cold read on demand — imperfect, but available at 2 a.m.
See what all five have in common? The AI never generates story; it generates pressure. Questions, options, counterarguments, diagnostics. You stay the writer; it plays the room.
Guardrails, and a word about privacy
That pullquote is the guardrail that matters most, so let me spell it out. If you're stuck on a scene and your first move is "write this scene for me," the machine's version now occupies the space where your version was going to grow. You'll anchor on it — its rhythm, its shape, its choices — even while rewriting it. But if your first move is "here's what I have, ask me what's wrong with it," you stay the author and the machine stays the assistant. Generated placeholder scenes have their place, as we covered last chapter — but only after your own thinking has happened, never instead of it.
Two more guardrails. First, never accept a note without a reason. If it says the second act sags, ask where and why. Sometimes the explanation is sharp; sometimes it collapses under one follow-up question, and that tells you the note was pattern-matching, not reading. Second, keep your drafting outside the chat. Write in Final Draft, or in plain-text Fountain, and bring pages to the AI the way you'd bring them to a trusted reader. The chat is the room. It is not the page.
Finally, privacy — worth thirty seconds of your attention because your script is an unproduced, unregistered asset. Consumer AI chats may be used to train future models unless you turn that off; both ChatGPT and Claude offer settings or account tiers that keep your inputs out of training. Check them before you upload a full draft, and consider registering your script with the U.S. Copyright Office or the WGA registry before sharing it widely — a habit that predates AI and still holds. I keep my most sensitive material — the twist, the ending, anything I'd be sick to see paraphrased somewhere — described in general terms rather than pasted verbatim. Probably overcautious. Cheap insurance.
The single most useful prompt I've ever run: I pasted a confrontation scene I'd rewritten six times and asked, "What does each character in this scene want, based only on what's on the page?" The answer came back wrong for my lead — and that was the gift. Her want was in my head, not in her lines. If a careful reading machine couldn't find it, no exhausted producer at 11 p.m. was going to. I fixed two lines. The scene finally worked.
You now have a working room. Next chapter we deal with the questions hanging over it: whose pages are these legally, why AI prose is average by design, and the rules — credit, copyright, disclosure — that keep your script sellable.
Everything Module 3 teaches, built into one tool — Scene Analysis reads your script and returns beat-by-beat structure, character, and pacing notes. Coverage-grade feedback on your draft, in minutes.