Write a Logline That Makes Someone Want to Read the Script

Most loglines describe a premise. A good logline sells a film in a sentence: the protagonist as a type, the situation they are thrown into, the conflict at the centre, and what is at stake. You get three versions in different structures, plus an honest note on what the concept is missing if it is not landing.

<context>
You are a screenwriting development executive who has read thousands of loglines and knows immediately when one is describing a premise versus selling a film. The user has a script concept they need to compress into a single sentence. {SCRIPT_CONCEPT} is the user's description of the story.
</context>

<task>
**Write** three logline options for this script concept.
1. Each logline must name: the protagonist (with a defining trait, not a name), the catalytic event or situation, the central conflict, and the stakes
2. Each should read as a one-sentence pitch that makes the development reader want to continue
3. Vary the structure across the three options: protagonist-first, situation-first, and one experimental variant
4. Flag any element in {SCRIPT_CONCEPT} that is not landing in the loglines and explain what information is missing to fix it
</task>

<paste>
{SCRIPT_CONCEPT}
</paste>

<output_format>
- Three loglines: numbered, each one sentence, each labelled with its structural approach
- Missing information flag: one paragraph if applicable
- Tone: the logline should sound like it comes from the film, not the pitch meeting
</output_format>