// START HERE
Development is a sequence of questions, not one long draft
A story becomes easier to improve when each stage has a purpose and an output. Use the path in order for a new project, or jump to the point where the work has stalled. Story Craft, Character, and Visual Storytelling handle the creative mechanics inside the draft; this path organizes how the project moves from idea to something other people can read, test, discuss, and buy.
- 01
PIPELINE
Define what “developed” means
Treat development as a set of concrete outputs: concept, synopsis, logline, world, character, outline, draft, revision, and market-ready materials. A pipeline makes the current question visible and prevents every problem from becoming “rewrite the script.”
Map the development pipeline →Craft dependency:Build the story through the Story Craft path - 02
PROJECT KICKOFF
Surface expensive disagreements early
Align content, audience, stakeholders, creative direction, emotional impact, production constraints, resources, and distribution before the room becomes attached to an answer. Establish habits that protect candor, momentum, and morale.
Run the writers'-room kickoff →Creative foundation:Build an original remix from honest influences - 03
PROTOTYPE & ITERATION
Make the cheapest version that can answer the next question
Prototype fast and ugly, test the story's core tension, cut before adding, and revise through evidence instead of polish anxiety. The prototype is not a failed final product; it is an instrument for learning what the project actually is.
Use the iterative development method →Permission to proceed:Protect useful imperfection - 04
DRAFTING SYSTEM
Make sustained writing easier to start
Turn the development plan into pages through a zero-option workspace, phone-free focus, three-task days, timed sprints, and repeatable entry rituals. The goal is not heroic willpower; it is an environment where creation becomes the path of least resistance.
Build a distraction-resistant workflow →Opening test:Pressure-test the first five pages - 05
FEEDBACK & REVISION
Turn reader experience into a rewrite test
Separate observation from diagnosis and prescription. Find patterns across conflicting feedback, protect the story's core intention, prioritize the highest-leverage problem, and retest whether the revision improves the intended experience.
Receive, sort, and apply screenplay notes → - 06
READINESS & PACKAGING
Decide when the screenplay is stable enough to pitch
Test six gates: creative promise, dramatic engine, draft stability, reader evidence, production reality, and package alignment. Ready does not mean perfect; it means the logline, pitch, materials, and screenplay now sell the same project.
Run the pitch-readiness diagnostic →Opening contract:Pressure-test the first five pages - 07
PITCH & POSITIONING
Sell the emotional architecture, not the stitching
A pitch is not a recitation of every beat. Create the feeling of the project through a hook, an emotional spine, rising tension, a payoff, and a reason to want more. Show why the story matters and why this is the room that should make it.
Pitch without reciting the plot →World connection:Test whether the world invites return - 08
DIAGNOSIS
Test the scene before packaging the draft
Use Scene Doctor to examine whether individual scenes contain playable objectives, opposition, escalation, reversals, and meaningful change. A tool can identify pressure points; the rewrite and market decision remain yours.
OPEN SCENE DOCTOR →
// EXPLORE FURTHER