Brainstorming & Idea Development
This is the one place in the whole pipeline where I let AI run loud and messy. A sparring partner that never gets tired, never gets precious, and throws a hundred punches so you can find the two worth keeping.
Welcome to Core Craft. For four chapters I've been telling you where to keep AI on a leash. Brainstorming is where you let it off — because at the idea stage, nothing is precious yet, nothing is on the page yet, and the failure mode of a bad suggestion is that you ignore it. This is the lowest-risk, highest-energy use of AI in the entire development process, and the method that makes it work is simple: treat it like a sparring partner, not an oracle.
A sparring partner doesn't tell you what to do. It throws things at you and watches what you do with them. In practice, that looks like sitting down with a half-formed notion — "something about a repo man," "two sisters and a funeral" — and making the machine hit you with premises, what-ifs, and world questions until something makes you sit up. You're not looking for a good idea in its output. You're looking for the output that makes your idea show up. Those are different events, and the second one is the only one that matters.
Volume, then taste
Here's the engine underneath all of it: generate twenty, keep one. AI's real gift to a brainstorming writer isn't quality — it's volume without fatigue. A human writing partner gets tired around variation seven and starts defending their favorites. The machine will give you twenty premises, then twenty more, with no ego in the game. Most will be mediocre. A few will be bad in instructive ways. And occasionally one contains a live wire — usually not the whole premise, just a phrase, a collision, a corner of it.
The part nobody tells you: the keeping is the writing. When you read twenty variations and your gut snags on one, your taste — the accumulated judgment of every film you've loved and every scene that's ever embarrassed you — is doing authorship. The machine supplied noise; you supplied the signal detector. That's why this doesn't compromise your voice the way generated pages do: nothing survives the brainstorm except what your judgment pulled out of the pile.
Here are the exercises I actually run, in the project we set up in Chapter 3:
- The twenty-premise sweep — give it your seed idea and ask for twenty distinct premises: different genres, different protagonists, different scales. Read fast, mark what snags.
- The what-if cascade — take your favorite and ask for fifteen "what if" complications: what if she's lying, what if it's twenty years later, what if the town knows. Escalations, reversals, inversions.
- World questions — "Ask me thirty questions about how this world works that I haven't thought about." Answering ten of them in your own head is a morning of real development.
- The stress test — make it interrogate the premise like a bored executive: who's the antagonist, why now, why this person and not anyone else? If the premise survives, outline it. If it doesn't, you just saved six months.
- The collision drill — feed it two unrelated obsessions of yours and ask for ten stories that need both. Forced marriages of your own material — this one punches above its weight.
Mine your own life first
One warning before you fall in love with this workflow. Remember what the machine is: a remix engine. AI recombines what already exists; it cannot supply what doesn't. If you start every project from a machine brainstorm, every project starts from the existing pile — other people's movies, reshuffled. The premises will feel familiar because they are, at the molecular level, familiar.
So the discipline is order of operations: your life first, the machine second. Before you open a chat, spend an hour with a notebook on the raw material only you have — the jobs you've worked, the funerals you've sat through, the argument in your family that never resolves, the thing you saw at nineteen you've never told anyone. That material is not in any training set. Bring that to the sparring session as the seed, and now the machine is remixing you — stress-testing and complicating something that already has a heartbeat. The difference in the output is not subtle. A premise with your fingerprints plus machine pressure beats a machine premise with your light polish every single time.
My best brainstorming session ever started with the worst output. I asked for twenty takes on a heist premise and all twenty were dull — but number fourteen put the heist at a wedding, which was wrong, and its wrongness annoyed me into realizing what the story actually was: not a heist at all, but a family that treats every gathering like a job. The machine never had the idea. It irritated the idea out of me. That's the sparring partner working exactly as intended.
So you've got a premise with a pulse. Next chapter, we turn it into the paperwork that sells it — loglines, synopses, and treatments, and how AI helps you build all three without sanding your voice off them.
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.
