1 - Last Chance
DeliveryAll three lenses are solid — worth protecting as it stands.
It restates its note rather than deepening it Development
HoldingThe reader can follow what matters.
Wakanda faces an imminent threat of war from Namor, and a group of military-types venture into the seas to find vibranium.
See other logline suggestions
Setting: Provide the time period, Provide the location
Themes: Death and Loss, Redemption, Technology, Betrayal, Family and Heritage, Responsibility, Culture Clash, Overcoming Adversity
Conflict & Stakes: Provide a summary of the primary conflicts and stakes in the story
Mood: Provide a description of the overall mood or tone of the screenplay
Standout Features:
Comparable Scripts: Black Panther, Iron Man 3, Aquaman, Avengers: Age of Ultron, Wonder Woman 1984, Avatar, The Lion King, Batman Begins
This section delivers a top-level assessment of the screenplay’s strengths and weaknesses — covering overall quality (P/C/R/HR), character development, emotional impact, thematic depth, narrative inconsistencies, and the story’s core philosophical conflict. It helps identify what’s resonating, what needs refinement, and how the script aligns with professional standards.
Breaks down your script along various categories.
Breaks down the emotional journey of the audience across the script.
Scenes now use the full 0–10 scale, so your numbers will look lower and more spread out than before. That's the new, smarter model being honest — not a verdict on your script.
A 5 is fine. “Functional” (5–6) is a solid, professional scene — that's where most scenes sit. The scale rides low on purpose, so it has room to point down (where to fix) and up (what's working).
The table uses the same colors: warm = worth a look · neutral = fine · green = working. We re-scored our whole reference library the same way, so your percentile rankings stay a fair, apples-to-apples comparison.
All of your scenes analyzed individually and compared, so you can zero in on what to improve.
This section looks at the extra spark — your story’s voice, style, world, and the moments that really stick. These insights might not change the bones of the script, but they can make it more original, more immersive, and way more memorable. It’s where things get fun, weird, and wonderfully you.
High-level overview
The movie revolves around Wakanda's defense against Namor's threat of war. After King T'Challa's death, Queen Ramonda defends Wakanda's vibranium policy while mercenaries attack a Mali outreach center. Wakandan forces foil the attack, and a group of military-types embark on a deep-sea mission to find vibranium, leading to tragedy. Namor seeks Wakanda's help to prevent further mining of vibranium. Shuri successfully recreates the Heart-Shaped Herb, becoming the Black Panther again, and presents a plan to weaken Namor through dehydration. They capture Namor and confront him about his violations of their agreement. In the end, Ross is taken into custody, Shuri says goodbye to Okoye, and reminisces about her brother T'Challa.
Scene by Scene Summaries
Act-by-act sequence summaries
Shuri frantically works to synthesize the Heart-Shaped Herb to revive her brother, but the process is too slow and the confidence rate too low; T'Challa dies. The sequence ends with his funeral in Wakanda, where Shuri mourns.
Queen Ramonda defends Wakanda at the UN, the Dora Milaje capture mercenaries, and evidence of French involvement is presented. Meanwhile, a CIA operation to detect vibranium in the ocean leads to a confrontation with the Talocanil, a hidden underwater nation. Namor emerges as a powerful new adversary, destroying the helicopter and making his presence known.
Shuri struggles with her grief while Ramonda tries to help her heal. Namor appears and issues an ultimatum: find the scientist or face war. The Wakandan council debates the options, and Shuri studies the captured vibranium detector. Ultimately, they decide to go to Everett Ross for help.
Shuri and Okoye locate Riri, warn her of danger, and then must escape a massive FBI raid on her garage. Using Riri's Ironheart suit, a Barracuda, and a motorcycle, they engage in a high-speed chase through Boston, culminating in Riri destroying a surveillance drone. The chase ends with the FBI neutralized, but the team is exhausted and unaware of the impending Talocanil attack.
As Shuri, Okoye, and Riri cross Harvard Bridge, they are ambushed by Namora, Attuma, and Talocanil warriors. Okoye fights valiantly but is overwhelmed, and Shuri is knocked unconscious. Riri is captured, and Shuri is taken by Namor's forces. The goal fails completely.
Ross investigates the crime scene and finds Shuri's kimoyo bead. Okoye reports to the Wakandan council, is stripped of rank for failing to protect Shuri, and is replaced by Ayo. Ross contacts Ramonda via the bead, revealing the capture and the existence of the student's laptop, which the CIA is trying to crack. Ramonda begins to formulate a plan.
Ramonda travels to Madagascar to confront Namor, who gives her a two-day ultimatum. She then goes to Haiti to recruit Nakia, who initially hesitates but agrees to use her espionage skills to find and rescue Shuri. Nakia begins her investigation, tracking down a Mayan elder who knows the location of the cenote entrance to Talocan.
Shuri awakens in a cave prison with Riri, then is taken to meet Namor. He tells her the tragic history of Talocan—how his people were transformed by a mutagenic plant and enslaved by colonizers. Shuri is shown the underwater city of Talocan, including the vibranium-powered Sastun. She offers to help him improve the light, beginning to build a rapport and a potential escape route.
Ross infiltrates the NSA facility, uses a trick to flush Shuri's kimoyo beads down the toilet to amplify the signal, and ensures the laptop remains uncracked. In Talocan, Shuri covertly builds a vibranium amplifier to create a homing signal while Riri distracts the guards. Nakia, on the surface, locates the cenote entrance and swims into Talocan, ready to retrieve Shuri by any means.
Shuri rejects Namor's demand to join him in striking the surface, and Ramonda tries to negotiate Riri's release. Namor threatens to execute Riri and to make Wakanda fall first. Nakia infiltrates the visitor quarters, subdues the Talocanil guards, and extracts Shuri and Riri. The three escape through an underwater cave, board Nakia's skirmisher, rendezvous with the Royal Talon Fighter, and reunite with Ramonda, who orders their return to Wakanda.
Namor returns to Talokan, declares the breach unforgivable, and orders Namora, Attuma, and their best warriors to attack Wakanda. In Wakanda, Nakia and Okoye reunite, Shuri is debriefed and begins weaponizing dehydration, Aneka returns, and Riri is placed under Ramonda's protection. The sequence closes with a Talocanil Siren spotted near the River Barrier, signaling that the attack is about to begin.
Hydrobombs and flooding turn the Golden City into a war zone. M'Baku, Okoye, Nakia, and the Dora Milaje fight through the flood while Ramonda and Riri pilot Scarab Beetles from the Council Room. Shuri and Aneka attack Namor, but he cripples their Sunbird. Namor reaches the Tribal Council, shatters the windows, and floods the chamber. Riri is revived, but Ramonda drowns. Namor issues the same ultimatum before withdrawing, leaving the city devastated and the queen dead.
Overwhelmed by Ramonda's death, Shuri walks into a river carrying a heavy weight, intending to die. Nakia and Okoye interrupt; Shuri turns her gauntlet on Okoye and lashes out at both for their perceived failures. Nakia refuses to leave, telling Shuri that her mother and brother wanted her to live and that Wakanda needs her. Shuri finally lowers the gauntlet and collapses into Nakia's arms.
Shuri buries Ramonda and tells M'Baku she has nothing left but vengeance; he promises the counsel he gave T'Challa and warns her not to bury herself in technology. Days later, WDG discovers a hydrobomb in the wreckage, and refugees relocate to Jabariland. Tribal elders fracture over choosing a new ruler, while Okoye's uncle urges her to claim the throne. Meanwhile, Ross warns Shuri that Washington is planning destabilization; Shuri reveals the Queen is dead and asks Ross to keep the U.S. at bay.
Ross buys time from Val and the CIA by arguing against an attack on Wakanda. Shuri analyzes Namora's hydrobomb, enlists Riri to teach her about combustion and petroleum—the key to weakening Namor with heat—and agrees to help build Ironheart's suit. In the lab, Shuri compares the Heart-Shaped Herb to Namor's mother's bracelet, uploads T'Challa's DNA, and constructs the Midnight Angel armor for Okoye, while Riri completes her Ironheart suit. The sequence ends with the counter-attack arsenal ready.
Shuri successfully recreates the herb, takes it, and enters the ancestral plane where she confronts Killmonger. She awakens determined, builds a new suit, and proves her strength to M'Baku, who accepts her as the Black Panther.
Shuri proposes drawing Namor out using a vibranium detector, then dehydrating and killing him. After debate, she gains support from M'Baku and others. They set the trap, and the ambush begins with the Royal Sea Leopard attacking the Talocanil.
The ambush escalates into a full battle. Namor is captured and sealed in the Royal Talon Fighter. However, the ship is attacked by Talocanil whales, causing massive damage. In the RTF, Shuri and Namor fight, and the plane crashes in the Atacama Desert.
Shuri fights Namor in the desert, both weakened. She spares him and offers an alliance, which he accepts. Meanwhile, the Wakandan forces at sea are aided by Okoye and Aneka, and the battle ends with Namor calling off his army. Shuri returns with Namor, and peace is restored.
Val reveals she knows about Wakanda and has bugged Ross's beads. She arrests him. During transport, Okoye, as a Midnight Angel, rescues Ross by attacking the guards and freeing him.
Namor accepts the alliance, Aneka becomes a Dora again, Riri gets her car. M'Baku challenges for the throne. Shuri goes to Haiti, says goodbye to Okoye, and meets Nakia's son, T'Challa's child, finding closure and hope.
Each axis shows your script's raw score (0–10) in that category. We recently upgraded the AI models behind these categories, so percentile rankings are temporarily unavailable while we re-score our reference library.
Hover over each axis on the radar chart to see what that category measures and why it matters.
Analysis: The screenplay effectively utilizes character development to drive the narrative and create emotional engagement. Characters undergo significant transformations, and their motivations and conflicts are well-explored. However, there is room for refinement in enhancing character complexity and ensuring consistent character growth throughout the story.
Analysis: The screenplay presents a compelling premise that sets up an intriguing conflict between Wakanda and Talocan, driven by the characters' motivations and the search for vibranium. However, it could benefit from further refining the narrative to enhance its clarity and audience engagement, particularly in the execution and depth of the conflict resolution.
Analysis: The screenplay exhibits a sturdy narrative structure and effectively balances its multiple plotlines, showcasing the clash between Wakanda and Talocan, while exploring themes of grief, legacy, and the responsibility of leadership. The screenplay deftly handles the task of balancing character arcs with the advancement of the central conflict, resulting in a compelling and engaging storyline. While the pacing remains steady throughout, there are moments where the plot could benefit from refinement to elevate the tension and emotional impact.
Analysis: The screenplay adeptly explores themes of identity, legacy, and the clash between tradition and progress through its well-developed characters and engaging narrative. While some areas could be refined to enhance thematic depth, the screenplay holds promise for delivering a thought-provoking and emotionally resonant experience.
Analysis: "Black Panther: Wakanda Forever" presents a richly imagined and visually captivating cinematic experience. The screenplay's imagery is characterized by its vivid and evocative descriptions of the vibrant Afro-futuristic world of Wakanda and its captivating underwater counterpart, Talocan.
Analysis: The screenplay elicits a range of emotions, with its strengths lying in the depth of emotional responses it evokes. However, there are opportunities to enhance the emotional depth and resonance by delving deeper into the characters' internal conflicts and exploring their motivations and backstories.
Analysis: The screenplay effectively presents conflict and stakes, although there are areas where they could be further enhanced to deepen tension and elevate audience engagement. The central conflict between Wakanda and Talocan is clear and compelling, with personal stakes that drive the characters' actions and decisions. However, some subplots lack the same level of significance and integration, potentially diluting the overall impact of the conflict.
Analysis: The screenplay displays an impressive level of originality and creativity in its blend of Afro-futuristic elements with a superhero narrative. The film's focus on Wakanda's distinct culture, its seamless integration of mythology, technology, and action sequences sets it apart from typical superhero films.
Expand to see detailed analysis
View Complete AnalysisProtagonist
Protagonist
Antagonist
Ironheart
Protagonist
Protagonist
| Theme | Theme Details | Theme Explanation |
|---|---|---|
|
Death and Loss
|
King T'Challa's death, mourning, and grieving are prominent throughout the screenplay.
|
The theme of death and loss is about coming to terms with the loss of loved ones and accepting the inevitability of death, coping with grief, and moving on. |
|
Redemption
|
Aneka seeks redemption after her past actions, and Namor offers it to her.
|
The theme of redemption deals with the idea of making amends for past misdeeds and finding a way to make up for past mistakes. |
|
Technology
|
Shuri's development of new technology and the creation of a new Black Panther are central to the plot of the screenplay.
|
The theme of technology is about innovation, scientific progress, and the impact of technology on society. |
|
Betrayal
|
Ross's ties to Wakanda are revealed, and he is placed under arrest. Namor violates an agreement and is held accountable.
|
The theme of betrayal explores the idea of trust and loyalty and the consequences of breaking them. |
|
Family and Heritage
|
Shuri and Nakia's relationship with Toussaint and the revelation of his identity as Prince T'Challa are significant to the plot.
|
The theme of family and heritage deals with the importance of relationships with family and cultural heritage, including traditions, customs, and ancestry. |
|
Responsibility
|
Shuri assumes the responsibility of developing new technology, creating a new Black Panther, and leading an attack on Namor.
|
The theme of responsibility explores the ethical and moral obligations that come with power, leadership, and authority. |
|
Culture Clash
|
Multiple instances of tension arise between different cultures: Wakandan, American, Haitian, Mayan, and Atlantean.
|
The theme of culture clash deals with the clashes that occur between different cultures as a result of misunderstandings or differences in values, beliefs, or customs. |
|
Overcoming Adversity
|
The characters face multiple obstacles and challenges, including the death of a loved one, hostage situations, betrayal, and attacks on their city.
|
The theme of overcoming adversity is about persevering through difficult circumstances and coming out stronger on the other side. |
| Site | Description |
|---|---|
| Studio Binder | Movie Themes: Examples of Common Themes for Screenwriters |
| Coverfly | Improving your Screenplay's theme |
| John August | Writing from Theme |
| Title | Description |
|---|---|
| Story, Plot, Genre, Theme - Screenwriting Basics | Screenwriting basics - beginner video |
| What is theme | Discussion on ways to layer theme into a screenplay. |
| Thematic Mistakes You're Making in Your Script | Common Theme mistakes and Philosophical Conflicts |
Everything above was written for you before you arrived. These are the things you can set running yourself, on the whole script or on one scene at a time.
Read them one at a time, or line them all up side by side.
Every scene is read two ways — Scene Mechanics (how the scene is built) and Craft Read (how it is written). Open any scene to see both.
All three lenses are solid — worth protecting as it stands.
It restates its note rather than deepening it Development
HoldingThe reader can follow what matters.
No lens is broken, but Design, Execution and Read are soft — this reads as a polish pass.
It plays close to the version we’ve seen before Freshness
HoldingThe reader can follow what matters.
A ritual beat repeats a known pattern on purpose, so movement and freshness read low by design.
All three lenses are solid — worth protecting as it stands.
It restates its note rather than deepening it Development
HoldingThe reader can follow what matters.
All three lenses are solid — worth protecting as it stands.
The situation deepens as it goes Development
HoldingThe reader can follow what matters.
No lens is broken, but Design, Execution and Read are soft — this reads as a polish pass.
It isn’t clearly about one thing yet Contract
HoldingA real force keeps it pushing forward.
All three lenses are solid — worth protecting as it stands.
The situation deepens as it goes Development
HoldingA real force keeps it pushing forward.
No lens is broken, but Design, Execution and Read are soft — this reads as a polish pass.
It isn’t clearly about one thing yet Contract
HoldingThe reader can follow what matters.
An aftermath beat lands the cost of what just happened rather than driving new action.
All three lenses are solid — worth protecting as it stands.
A real force keeps it pushing forward Pressure
HoldingThe reader can follow what matters.
All three lenses are solid — worth protecting as it stands.
What happens here obliges what comes next Consequence
HoldingThe reader can follow what matters.
A ritual beat repeats a known pattern on purpose, so movement and freshness read low by design.
All three lenses are solid — worth protecting as it stands.
The situation deepens as it goes Development
HoldingThe reader can follow what matters.
No lens is broken, but Design and Read are soft — this reads as a polish pass.
It restates its note rather than deepening it Development
HoldingThe reader can follow what matters.
No lens is broken, but Design and Read are soft — this reads as a polish pass.
It restates its note rather than deepening it Development
HoldingThe reader can follow what matters.
All three lenses are solid — worth protecting as it stands.
A real force keeps it pushing forward Pressure
HoldingThe reader can follow what matters.
All three lenses are solid — worth protecting as it stands.
The situation deepens as it goes Development
HoldingA real force keeps it pushing forward.
All three lenses are solid — worth protecting as it stands.
The situation deepens as it goes Development
HoldingThe reader can follow what matters.
All three lenses are solid — worth protecting as it stands.
It restates its note rather than deepening it Development
HoldingIt commits to one clear thing and holds it.
No lens is broken, but Design, Execution and Read are soft — this reads as a polish pass.
It isn’t clearly about one thing yet Contract
HoldingA real force keeps it pushing forward.
No lens is broken, but Design, Execution and Read are soft — this reads as a polish pass.
It isn’t clearly about one thing yet Contract
HoldingA real force keeps it pushing forward.
All three lenses are solid — worth protecting as it stands.
The situation deepens as it goes Development
HoldingA real force keeps it pushing forward.
No lens is broken, but Design and Read are soft — this reads as a polish pass.
It leans on mood instead of something actually pushing it Pressure
HoldingWhat happens here obliges what comes next.
All three lenses are solid — worth protecting as it stands.
The situation deepens as it goes Development
HoldingWhat happens here obliges what comes next.
An aftermath beat lands the cost of what just happened rather than driving new action.
No lens is broken, but Design and Read are soft — this reads as a polish pass.
It leans on mood instead of something actually pushing it Pressure
HoldingThe reader can follow what matters.
A transition carries us between beats. It owes less structurally than a scene built to turn.
No lens is broken, but Design and Read are soft — this reads as a polish pass.
It leans on mood instead of something actually pushing it Pressure
HoldingWhat happens here obliges what comes next.
All three lenses are solid — worth protecting as it stands.
The situation deepens as it goes Development
HoldingWhat happens here obliges what comes next.
All three lenses are solid — worth protecting as it stands.
The situation deepens as it goes Development
HoldingThe reader can follow what matters.
No lens is broken, but Design and Read are soft — this reads as a polish pass.
It leans on mood instead of something actually pushing it Pressure
HoldingThe reader can follow what matters.
An orientation beat sets up the world. It isn’t expected to carry a big turn, so a lower Design read here is often the shape of the scene, not a fault.
Design and Read are broken — this reads as a rebuild before polish.
It ends about where it started Movement
HoldingThe reader can follow what matters.
Read is broken — a load-bearing lens isn’t doing its job yet.
It plays close to the version we’ve seen before Freshness
HoldingThe reader can follow what matters.
A montage compresses time. It isn’t built to turn on a single thread.
No lens is broken, but Design and Read are soft — this reads as a polish pass.
It leans on mood instead of something actually pushing it Pressure
HoldingThe reader can follow what matters.
No lens is broken, but Read is soft — this reads as a polish pass.
There’s avoidable waste on the page Economy
HoldingThe reader can follow what matters.
No lens is broken, but Design and Read are soft — this reads as a polish pass.
It leans on mood instead of something actually pushing it Pressure
HoldingThe reader can follow what matters.
All three lenses are solid — worth protecting as it stands.
It restates its note rather than deepening it Development
HoldingThe reader can follow what matters.
Read is broken — a load-bearing lens isn’t doing its job yet.
It ends about where it started Movement
HoldingThe reader can follow what matters.
All three lenses are solid — worth protecting as it stands.
The situation deepens as it goes Development
HoldingIt commits to one clear thing and holds it.
No lens is broken, but Execution and Read are soft — this reads as a polish pass.
It isn’t clearly about one thing yet Contract
HoldingWhat happens here obliges what comes next.
No lens is broken, but Design, Execution and Read are soft — this reads as a polish pass.
It isn’t clearly about one thing yet Contract
HoldingThe reader can follow what matters.
An aftermath beat lands the cost of what just happened rather than driving new action.
No lens is broken, but Design, Execution and Read are soft — this reads as a polish pass.
It leans on mood instead of something actually pushing it Pressure
HoldingWhat happens here obliges what comes next.
No lens is broken, but Design, Execution and Read are soft — this reads as a polish pass.
It isn’t clearly about one thing yet Contract
HoldingA real force keeps it pushing forward.
An aftermath beat lands the cost of what just happened rather than driving new action.
All three lenses are solid — worth protecting as it stands.
It plays close to the version we’ve seen before Freshness
HoldingThe reader can follow what matters.
No lens is broken, but Design, Execution and Read are soft — this reads as a polish pass.
It isn’t clearly about one thing yet Contract
HoldingThe reader can follow what matters.
An aftermath beat lands the cost of what just happened rather than driving new action.
Read is broken — a load-bearing lens isn’t doing its job yet.
It isn’t clearly about one thing yet Contract
HoldingA real force keeps it pushing forward.
No lens is broken, but Design, Execution and Read are soft — this reads as a polish pass.
It isn’t clearly about one thing yet Contract
HoldingA real force keeps it pushing forward.
All three lenses are solid — worth protecting as it stands.
The situation deepens as it goes Development
HoldingWhat happens here obliges what comes next.
An aftermath beat lands the cost of what just happened rather than driving new action.
No lens is broken, but Read is soft — this reads as a polish pass.
It plays close to the version we’ve seen before Freshness
HoldingThe reader can follow what matters.
An aftermath beat lands the cost of what just happened rather than driving new action.
All three lenses are solid — worth protecting as it stands.
A real force keeps it pushing forward Pressure
HoldingThe reader can follow what matters.
No lens is broken, but Design, Execution and Read are soft — this reads as a polish pass.
It isn’t clearly about one thing yet Contract
HoldingWhat happens here obliges what comes next.
No lens is broken, but Design and Read are soft — this reads as a polish pass.
It leans on mood instead of something actually pushing it Pressure
HoldingThe reader can follow what matters.
All three lenses are solid — worth protecting as it stands.
A real force keeps it pushing forward Pressure
HoldingThe reader can follow what matters.
No lens is broken, but Design, Execution and Read are soft — this reads as a polish pass.
It ends about where it started Movement
HoldingThe reader can follow what matters.
A montage compresses time. It isn’t built to turn on a single thread.
All three lenses are solid — worth protecting as it stands.
It’s a fresh take on this kind of scene Freshness
HoldingThe reader can follow what matters.
A ritual beat repeats a known pattern on purpose, so movement and freshness read low by design.
All three lenses are solid — worth protecting as it stands.
It plays close to the version we’ve seen before Freshness
HoldingThe reader can follow what matters.
All three lenses are solid — worth protecting as it stands.
It restates its note rather than deepening it Development
HoldingA real force keeps it pushing forward.
A ritual beat repeats a known pattern on purpose, so movement and freshness read low by design.
All three lenses are solid — worth protecting as it stands.
A real force keeps it pushing forward Pressure
HoldingThe reader can follow what matters.
No lens is broken, but Design, Execution and Read are soft — this reads as a polish pass.
It isn’t clearly about one thing yet Contract
HoldingThe reader can follow what matters.
Design is broken — a load-bearing lens isn’t doing its job yet.
It restates its note rather than deepening it Development
HoldingEvery beat and line earns its place.
No lens is broken, but Design, Execution and Read are soft — this reads as a polish pass.
It isn’t clearly about one thing yet Contract
HoldingA real force keeps it pushing forward.
Design is broken — a load-bearing lens isn’t doing its job yet.
It restates its note rather than deepening it Development
All three lenses are solid — worth protecting as it stands.
There’s avoidable waste on the page Economy
HoldingA real force keeps it pushing forward.
No lens is broken, but Design, Execution and Read are soft — this reads as a polish pass.
It plays close to the version we’ve seen before Freshness
HoldingA real force keeps it pushing forward.
No lens is broken, but Design, Execution and Read are soft — this reads as a polish pass.
It isn’t clearly about one thing yet Contract
HoldingA real force keeps it pushing forward.
All three lenses are solid — worth protecting as it stands.
It restates its note rather than deepening it Development
HoldingIt turns — something is different by the end.
All three lenses are solid — worth protecting as it stands.
The situation deepens as it goes Development
HoldingWhat happens here obliges what comes next.
Design is broken — a load-bearing lens isn’t doing its job yet.
It restates its note rather than deepening it Development
HoldingEvery beat and line earns its place.
No lens is broken, but Design and Read are soft — this reads as a polish pass.
It leans on mood instead of something actually pushing it Pressure
HoldingThe reader can follow what matters.
An aftermath beat lands the cost of what just happened rather than driving new action.
No lens is broken, but Design and Read are soft — this reads as a polish pass.
It leans on mood instead of something actually pushing it Pressure
HoldingThe reader can follow what matters.
A ritual beat repeats a known pattern on purpose, so movement and freshness read low by design.
All three lenses are solid — worth protecting as it stands.
It leans on mood instead of something actually pushing it Pressure
HoldingIt turns — something is different by the end.
No lens is broken, but Design and Read are soft — this reads as a polish pass.
It leans on mood instead of something actually pushing it Pressure
HoldingEvery beat and line earns its place.
Your scene scores are compared against professional produced screenplays in our vault (The Matrix, Breaking Bad, etc.). The percentile shows where you rank compared to these films.
Example: A score of 8.5 in Dialogue might be 85th percentile (strong!), while the same 8.5 in Conflict might only be 50th percentile (needs work). The percentile tells you what your raw scores actually mean.
Hover over each axis on the radar chart to see what that category measures and why it matters.
“Functional” (5–6) is a solid, professional scene — that's where most scenes sit. The scale rides low on purpose, so it has room to point down (where to fix) and up (what's working).
Scenes now use the full 0–10 scale, so your numbers will look lower and more spread out than before. That's the new, smarter model being honest — not a verdict on your script.
The table below uses the same colors: warm = worth a look · neutral = fine · green = working. The point is awareness, not maxing every number — a scene can be light on plot or conflict for good reasons.
| Compelled to Read | Story Content | Character Development | Scene Elements | Audience Engagement | Technical Aspects | |||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Click for Full Analysis | Triage | Design | Overall | Clarity | Scene Impact | Concept | Plot | Originality | Characters | Character Changes | Internal Goal | External Goal | Conflict | Opposition | High stakes | Story forward | Twist | Emotional Impact | Dialogue | Engagement | Pacing | Formatting | Structure | |
| 1 - Last Chance | KeepDeliveryAll three lenses are solid — worth protecting as it stands. | SolidThe story machine is built and mostly working. | 7.2 | 9 / 9 | 9 / 8.5 | 8 | 7 | 6.5 | 8 | 6 | 8 | 9 | 7 | 6 | 8.5 | 7 | 8 | 8 | 7 | 7.5 | 7 | 9 | 8 | |
| 2 - T'Challa's Funeral | PolishRitualNo lens is broken, but Design, Execution and Read are soft — this reads as a polish pass. | SoftThe structure works but is leaking power in places. | 6.5 | 8.5 / 7.5 | 5.5 / 6 | 7 | 5 | 6 | 6 | 4 | 6 | 5 | 2 | 1 | 4 | 3.5 | 3 | 7 | 4 | 6 | 5.5 | 7.5 | 5.5 | |
| 3 - UN Ambush | KeepContestAll three lenses are solid — worth protecting as it stands. | SolidThe story machine is built and mostly working. | 6.5 | 9 / 8 | 5 / 6.5 | 7 | 6 | 5 | 7 | 2 | 5 | 7 | 7 | 7 | 7 | 6 | 4 | 5 | 7 | 6 | 5.5 | 9 | 6 | |
| 4 - Hostage Crisis and Diplomatic Tensions | KeepPursuitAll three lenses are solid — worth protecting as it stands. | SolidThe story machine is built and mostly working. | 6.5 | 7 / 7.5 | 8 / 7.5 | 7 | 7 | 7 | 7 | 2 | 6 | 8 | 7 | 6 | 7.5 | 7 | 8 | 6 | 7 | 7.5 | 6.5 | 8 | 6.5 | |
| 5 - Deep-Sea Disaster | PolishInvestigationNo lens is broken, but Design, Execution and Read are soft — this reads as a polish pass. | SoftThe structure works but is leaking power in places. | 5.5 | 8.5 / 7 | 8 / 7.5 | 6 | 6 | 5 | 3 | 1 | 3 | 6 | 7 | 8 | 7 | 6.5 | 5 | 4 | 4 | 6.5 | 7 | 8 | 6.5 | |
| 6 - Talocanil Invasion at Sea | KeepPursuitAll three lenses are solid — worth protecting as it stands. | SolidThe story machine is built and mostly working. | 6.5 | 8.5 / 8 | 8 / 7.5 | 7 | 6 | 5.5 | 4 | 1 | 4 | 7 | 8 | 8 | 7 | 7.5 | 7 | 6 | 5 | 7.5 | 8 | 9 | 7 | |
| 7 - Attacks and Explosions | PolishAftermathNo lens is broken, but Design, Execution and Read are soft — this reads as a polish pass. | SoftThe structure works but is leaking power in places. | 7.2 | 8.5 / 8 | 9 / 8.5 | 8 | 7 | 7.5 | 6 | 4 | 5 | 7 | 9 | 9 | 9 | 9 | 9 | 7 | 6 | 8 | 8 | 8 | 7.5 | |
| 8 - Shuri and Ramonda's Conversation | KeepRelationship shiftAll three lenses are solid — worth protecting as it stands. | SolidThe story machine is built and mostly working. | 6.5 | 8.5 / 8 | 5 / 6.5 | 7 | 6 | 5 | 7 | 4 | 7 | 6 | 5 | 4 | 5 | 4 | 4 | 7 | 7 | 6.5 | 6 | 8 | 6.5 | |
| 9 - Grief and Rituals | KeepRitualAll three lenses are solid — worth protecting as it stands. | SolidThe story machine is built and mostly working. | 6.8 | 9 / 8.5 | 7 / 7.5 | 8 | 7 | 6.5 | 7 | 6 | 8 | 6 | 8 | 6 | 6 | 5 | 6 | 8 | 7 | 7 | 7.5 | 9 | 7.5 | |
| 10 - Namor Brings a Threat to Wakanda | KeepInvestigationAll three lenses are solid — worth protecting as it stands. | SolidThe story machine is built and mostly working. | 6.8 | 8.5 / 8 | 8.5 / 8 | 8 | 7 | 8 | 7 | 3 | 6.5 | 7 | 8 | 8 | 8.5 | 7.5 | 9 | 6 | 7 | 7.5 | 7 | 8 | 6.5 | |
| 11 - Tribal Council Meeting | PolishDeliberationNo lens is broken, but Design and Read are soft — this reads as a polish pass. | SoftThe structure works but is leaking power in places. | 6.5 | 9 / 8.5 | 6.5 / 7.5 | 8 | 7 | 6.5 | 7 | 3 | 7 | 8 | 8 | 8 | 8 | 6.5 | 6 | 6 | 7 | 7 | 6 | 9 | 6.5 | |
| 12 - The Vibranium Detector | PolishInvestigationNo lens is broken, but Design and Read are soft — this reads as a polish pass. | SoftThe structure works but is leaking power in places. | 6.2 | 8.5 / 8 | 7 / 7.5 | 7 | 6 | 7 | 7 | 2 | 6 | 7 | 2 | 1 | 4 | 6.5 | 6 | 4 | 6 | 5.5 | 5 | 8 | 5.5 | |
| 13 - Finding the Scientist | KeepDeliveryAll three lenses are solid — worth protecting as it stands. | SolidThe story machine is built and mostly working. | 6.5 | 9 / 8.5 | 8 / 7.5 | 8 | 7 | 7 | 7 | 3 | 6 | 8 | 6 | 4 | 7 | 7 | 8 | 5 | 7 | 7 | 6.5 | 8 | 6.5 | |
| 14 - Riri's Garage Raid | KeepPursuitAll three lenses are solid — worth protecting as it stands. | SolidThe story machine is built and mostly working. | 6.5 | 9 / 8 | 8 / 7.5 | 7 | 7 | 7 | 7 | 5 | 6 | 8 | 8 | 8 | 8 | 7 | 7 | 6 | 7 | 8 | 7 | 8 | 7 | |
| 15 - Escape from Riri's Garage | KeepPursuitAll three lenses are solid — worth protecting as it stands. | SolidThe story machine is built and mostly working. | 6.5 | 8.5 / 8 | 8 / 7.5 | 7 | 7 | 7.5 | 6 | 4 | 6 | 8 | 8 | 7 | 8 | 8 | 7 | 6 | 6 | 7.5 | 7.5 | 8 | 7 | |
| 16 - Escape from Cambridge | KeepPursuitAll three lenses are solid — worth protecting as it stands. | SolidThe story machine is built and mostly working. | 6.5 | 7.5 / 8 | 7 / 6.5 | 7 | 6 | 6 | 7 | 1 | 4 | 8 | 8 | 5 | 7 | 5 | 4 | 6 | 6 | 7.5 | 7.5 | 8 | 7 | |
| 17 - Escape from Cambridge | PolishPursuitNo lens is broken, but Design, Execution and Read are soft — this reads as a polish pass. | SoftThe structure works but is leaking power in places. | 6.5 | 6.5 / 7 | 8 / 7.5 | 8 | 6 | 7 | 7 | 2 | 6 | 8 | 8 | 7 | 7 | 6 | 7 | 5 | 5 | 7.5 | 6.5 | 5 | 5.5 | |
| 18 - High-Flying Rescue | PolishPursuitNo lens is broken, but Design, Execution and Read are soft — this reads as a polish pass. | SoftThe structure works but is leaking power in places. | 6.8 | 8.5 / 7.5 | 7.5 / 7.8 | 7 | 7 | 6.5 | 6 | 2 | 5 | 8 | 8 | 6 | 8 | 7.5 | 7 | 7 | 6 | 7.5 | 8 | 8.5 | 7 | |
| 19 - Bridge Battle | KeepPursuitAll three lenses are solid — worth protecting as it stands. | SolidThe story machine is built and mostly working. | 6.5 | 7 / 7.5 | 8.5 / 7.5 | 7 | 7 | 6.5 | 6 | 5 | 6 | 7 | 8 | 8 | 8 | 8 | 7 | 6 | 6 | 7.5 | 7 | 7 | 6.5 | |
| 20 - Escape from Cambridge | PolishInvestigationNo lens is broken, but Design and Read are soft — this reads as a polish pass. | SoftThe structure works but is leaking power in places. | 6.5 | 9 / 8.5 | 7.5 / 7.5 | 7 | 7 | 5.5 | 7 | 4 | 5.5 | 7 | 6 | 7 | 6.5 | 7 | 6 | 5 | 7 | 6.5 | 6.5 | 8 | 6.5 | |
| 21 - Okoye Loses Everything | KeepAftermathAll three lenses are solid — worth protecting as it stands. | SolidThe story machine is built and mostly working. | 6.5 | 8.5 / 8 | 7.5 / 7.5 | 7 | 7 | 6 | 7 | 6 | 7 | 8 | 8 | 8 | 7 | 6 | 5 | 7 | 7 | 7 | 6.5 | 8 | 6.5 | |
| 22 - In Pursuit of Wakandans | PolishTransitionNo lens is broken, but Design and Read are soft — this reads as a polish pass. | SoftThe structure works but is leaking power in places. | 6.5 | 9 / 8.5 | 7.5 / 7.5 | 7 | 6 | 6.5 | 7 | 2 | 7 | 8 | 6 | 8 | 7 | 7 | 6 | 5 | 6 | 7 | 6.5 | 8 | 7 | |
| 23 - Rescue Mission | PolishDeliveryNo lens is broken, but Design and Read are soft — this reads as a polish pass. | SoftThe structure works but is leaking power in places. | 6.5 | 9 / 8.5 | 7.5 / 7.5 | 7 | 7 | 6 | 6 | 2 | 6 | 8 | 6 | 4 | 7 | 7.5 | 4 | 5 | 7 | 6.5 | 6.5 | 9 | 6 | |
| 24 - Ramonda's Ultimatum | KeepNegotiationAll three lenses are solid — worth protecting as it stands. | SolidThe story machine is built and mostly working. | 7.2 | 9 / 8.5 | 8 / 8 | 8 | 7 | 7 | 8 | 5 | 7.5 | 8 | 9 | 8 | 8.5 | 8 | 7 | 8 | 7 | 7.5 | 7.5 | 8 | 7 | |
| 25 - untitled | KeepInvestigationAll three lenses are solid — worth protecting as it stands. | SolidThe story machine is built and mostly working. | 6.5 | 8.5 / 8 | 7 / 7.5 | 7 | 6 | 5.5 | 7 | 5 | 7 | 6 | 5 | 4 | 7 | 6 | 5 | 8 | 7 | 6.5 | 6 | 8 | 6.5 | |
| 26 - Captives and Culture | PolishOrientationNo lens is broken, but Design and Read are soft — this reads as a polish pass. | SoftThe structure works but is leaking power in places. | 6.5 | 8.5 / 8 | 7 / 7.5 | 7 | 6 | 5.5 | 7 | 3 | 7 | 6 | 4 | 3 | 7 | 6 | 4 | 6 | 6 | 6.5 | 7 | 8 | 6 | |
| 27 - Namor's Custody | Low on its ownDeliveryDesign and Read are broken — this reads as a rebuild before polish. | BrokenThe underlying story machine isn’t holding — worth looking at before polish. | 6.5 | 9 / 7.5 | 6 / 7 | 7 | 6 | 6.5 | 7 | 3 | 6 | 5 | 4 | 4 | 5 | 4 | 6 | 6 | 6 | 6 | 5.5 | 8 | 5.5 | |
| 28 - Namor's Origin Story | ReworkMontageRead is broken — a load-bearing lens isn’t doing its job yet. | SoftThe structure works but is leaking power in places. | 6.5 | 8.5 / 7.5 | 5 / 6.5 | 8 | 6 | 7 | 6 | 4.5 | 5 | 7 | 7 | 5 | 7.5 | 7 | 5 | 6 | 5 | 6 | 5.5 | 8 | 6.5 | |
| 29 - Namor's Duty | PolishDeliveryNo lens is broken, but Design and Read are soft — this reads as a polish pass. | SoftThe structure works but is leaking power in places. | 7.2 | 9 / 8 | 8 / 8.5 | 9 | 7 | 7.5 | 8 | 3.5 | 7 | 6.5 | 7 | 8 | 7.5 | 5.5 | 7 | 7 | 7 | 7 | 6 | 8.5 | 7 | |
| 30 - Revelations in Talocan | PolishInvestigationNo lens is broken, but Read is soft — this reads as a polish pass. | SolidThe story machine is built and mostly working. | 6.5 | 8 / 7.5 | 6 / 7 | 8 | 6 | 7.5 | 7 | 3 | 7 | 6 | 5 | 5 | 6 | 6 | 6 | 7 | 6 | 6.5 | 5.5 | 8 | 6.5 | |
| 31 - Infiltrating the NSA Facility | PolishDeliveryNo lens is broken, but Design and Read are soft — this reads as a polish pass. | SoftThe structure works but is leaking power in places. | 6.5 | 9 / 8 | 7 / 7.5 | 7 | 6 | 4.5 | 6 | 1 | 4 | 8 | 4 | 3 | 6 | 6 | 5 | 4 | 6 | 6 | 6 | 8 | 5.5 | |
| 32 - Retrieving the Thumb Drive | KeepDeliveryAll three lenses are solid — worth protecting as it stands. | SolidThe story machine is built and mostly working. | 7.2 | 9 / 8.5 | 8 / 7.5 | 8 | 7 | 7 | 7 | 2 | 5 | 9 | 7 | 6 | 6 | 8 | 7 | 4 | 7 | 7.5 | 7.8 | 8.5 | 7.5 | |
| 33 - Mission to Talocan | ReworkDeliveryRead is broken — a load-bearing lens isn’t doing its job yet. | SoftThe structure works but is leaking power in places. | 6.5 | 8.5 / 8 | 8 / 7.5 | 8 | 7 | 7.5 | 7 | 4 | 6.5 | 8 | 5 | 6 | 7.5 | 8 | 6 | 6 | 7 | 7 | 6.5 | 8.5 | 7 | |
| 34 - Alliances and Ultimatums | KeepNegotiationAll three lenses are solid — worth protecting as it stands. | SolidThe story machine is built and mostly working. | 6.5 | 9 / 8.5 | 7 / 7.5 | 8 | 6 | 7.5 | 7 | 3 | 7 | 7.5 | 8 | 8 | 8.5 | 6.5 | 5 | 7 | 7 | 7 | 6 | 8 | 6.5 | |
| 35 - Escape from the Talocanil Cave | PolishRescueNo lens is broken, but Execution and Read are soft — this reads as a polish pass. | SolidThe story machine is built and mostly working. | 6.5 | 7 / 7.5 | 8 / 8 | 7 | 7 | 6 | 7 | 5 | 7 | 8 | 8 | 7 | 9 | 8 | 7 | 6 | 6 | 7.5 | 6.5 | 7 | 6.5 | |
| 36 - Return to Wakanda | PolishAftermathNo lens is broken, but Design, Execution and Read are soft — this reads as a polish pass. | SoftThe structure works but is leaking power in places. | 6.5 | 9 / 8.5 | 7 / 7.5 | 7 | 6 | 5.5 | 7 | 3 | 6 | 5 | 4 | 2 | 7 | 7 | 5 | 7 | 6 | 6.5 | 6 | 8 | 5.5 | |
| 37 - Namor's Betrayal | PolishDeliveryNo lens is broken, but Design, Execution and Read are soft — this reads as a polish pass. | SoftThe structure works but is leaking power in places. | 6.5 | 9 / 8.5 | 8 / 7.5 | 7 | 7 | 5.5 | 6 | 5 | 7 | 8 | 8 | 6 | 8 | 8 | 5 | 6 | 6 | 7 | 7.5 | 8 | 7 | |
| 38 - Threats and Escapes | PolishAftermathNo lens is broken, but Design, Execution and Read are soft — this reads as a polish pass. | SoftThe structure works but is leaking power in places. | 5.5 | 7 / 7 | 6 / 7 | 6 | 6 | 5.5 | 6 | 4 | 6 | 6 | 4 | 3 | 7 | 6 | 4 | 5 | 5 | 5.5 | 5 | 7 | 5 | |
| 39 - Under Attack | KeepRelationship shiftAll three lenses are solid — worth protecting as it stands. | SolidThe story machine is built and mostly working. | 6.5 | 8.5 / 7.5 | 7 / 7.5 | 7 | 7 | 6.5 | 7 | 4 | 6 | 7 | 7 | 7 | 8 | 7 | 7 | 7 | 6 | 6.5 | 6 | 7.5 | 6.5 | |
| 40 - Attack on the Golden City | PolishAftermathNo lens is broken, but Design, Execution and Read are soft — this reads as a polish pass. | SoftThe structure works but is leaking power in places. | 6.5 | 7 / 7.5 | 7 / 7 | 7 | 7 | 6.5 | 6 | 4 | 6 | 8 | 7 | 7 | 8 | 8 | 7 | 6 | 6 | 7 | 6.5 | 7 | 6 | |
| 41 - Under Attack | ReworkPursuitRead is broken — a load-bearing lens isn’t doing its job yet. | SoftThe structure works but is leaking power in places. | 6.5 | 5.5 / 5 | 8 / 8 | 9 | 6 | 8 | 6 | 2 | 3 | 7 | 9 | 8 | 9 | 7 | 7 | 6 | 5 | 7.5 | 6.5 | 6 | 5.5 | |
| 42 - Namor Attacks | PolishPursuitNo lens is broken, but Design, Execution and Read are soft — this reads as a polish pass. | SoftThe structure works but is leaking power in places. | 6.5 | 6.5 / 7 | 9 / 8.5 | 7 | 6 | 6.5 | 6 | 2 | 5 | 7 | 8 | 8 | 9 | 9 | 7 | 6 | 6 | 7.5 | 6.5 | 7 | 5.5 | |
| 43 - Namor Attacks | KeepAftermathAll three lenses are solid — worth protecting as it stands. | SolidThe story machine is built and mostly working. | 7.5 | 8.5 / 9 | 9.5 / 9 | 9 | 8 | 8 | 8 | 8.5 | 8 | 7.5 | 10 | 10 | 10 | 9.5 | 9 | 9 | 7 | 9 | 8.5 | 9 | 8.5 | |
| 44 - Shuri's Grief | PolishAftermathNo lens is broken, but Read is soft — this reads as a polish pass. | SolidThe story machine is built and mostly working. | 6.5 | 9 / 8.5 | 7 / 7.5 | 8 | 6 | 7.5 | 7 | 6 | 8.5 | 7 | 8 | 7 | 8.5 | 4 | 7 | 8 | 7 | 7.5 | 6 | 9 | 6.5 | |
| 45 - Mourning and Decision Making | KeepRelationship shiftAll three lenses are solid — worth protecting as it stands. | SolidThe story machine is built and mostly working. | 6.5 | 9 / 8.5 | 6.5 / 7.5 | 7 | 6 | 5.5 | 7 | 2 | 7.5 | 7 | 5 | 3 | 6 | 5 | 6 | 6 | 8 | 6.5 | 6 | 9 | 7 | |
| 46 - Tribal Council Meeting and Okoye's Offer | PolishRelationship shiftNo lens is broken, but Design, Execution and Read are soft — this reads as a polish pass. | SoftThe structure works but is leaking power in places. | 6.2 | 9 / 8 | 5.5 / 7 | 6 | 6 | 4.5 | 7 | 2 | 6 | 7 | 6 | 5 | 7 | 7 | 4 | 5 | 6 | 6 | 5.5 | 8 | 6 | |
| 47 - Shuri's Call with Ross | PolishDeliveryNo lens is broken, but Design and Read are soft — this reads as a polish pass. | SoftThe structure works but is leaking power in places. | 6.5 | 9 / 8 | 6 / 7 | 7 | 6 | 5 | 6 | 4 | 6 | 7 | 5 | 4 | 7 | 7 | 5 | 6 | 6 | 6 | 6.5 | 8 | 5.5 | |
| 48 - Building A Plan | KeepInvestigationAll three lenses are solid — worth protecting as it stands. | SolidThe story machine is built and mostly working. | 6.5 | 9 / 8.5 | 7 / 7.5 | 7 | 7 | 5.5 | 6 | 2 | 7 | 8 | 6 | 6 | 8 | 8 | 5 | 6 | 7 | 6.5 | 7.5 | 9 | 7 | |
| 49 - Shuri's Revenge Plan | PolishMontageNo lens is broken, but Design, Execution and Read are soft — this reads as a polish pass. | SoftThe structure works but is leaking power in places. | 6.5 | 8.5 / 8 | 8 / 8 | 8 | 7 | 7 | 7 | 6 | 7 | 8 | 5 | 6 | 8 | 8.5 | 5 | 6 | 6 | 6.5 | 6 | 7 | 5.5 | |
| 50 - The Heart-Shaped Herb | KeepRitualAll three lenses are solid — worth protecting as it stands. | SolidThe story machine is built and mostly working. | 7.5 | 9 / 9 | 9 / 8.5 | 8 | 8 | 7.5 | 8 | 7 | 8 | 9 | 6 | 5 | 8 | 9 | 6 | 8 | 7 | 8 | 8 | 9 | 8 | |
| 51 - Revelation in the Ancestral Plane | KeepThematic argumentAll three lenses are solid — worth protecting as it stands. | SolidThe story machine is built and mostly working. | 7.5 | 9 / 9 | 8.5 / 8 | 9 | 7 | 9 | 8 | 8 | 9 | 8 | 8 | 9 | 9 | 8 | 9 | 8 | 9 | 8.5 | 8 | 9 | 8 | |
| 52 - The Return of the Black Panther | KeepRitualAll three lenses are solid — worth protecting as it stands. | SolidThe story machine is built and mostly working. | 7.2 | 8.5 / 8 | 7 / 8 | 8 | 8 | 6.5 | 8 | 7 | 7 | 8.5 | 7 | 6 | 7 | 8.5 | 5 | 6 | 7 | 7.5 | 7 | 8 | 7.5 | |
| 53 - The Plan to Fight Namor | KeepDeliberationAll three lenses are solid — worth protecting as it stands. | SolidThe story machine is built and mostly working. | 7.2 | 9 / 8.5 | 8 / 8 | 8 | 7 | 7 | 8 | 6 | 8 | 8 | 9 | 8 | 9 | 8 | 8 | 8 | 7 | 8 | 7.5 | 8 | 7.5 | |
| 54 - Pre-Battle Preparations | PolishDeliveryNo lens is broken, but Design, Execution and Read are soft — this reads as a polish pass. | SoftThe structure works but is leaking power in places. | 6.5 | 9 / 8.5 | 8 / 7.5 | 7 | 7 | 5.5 | 6 | 1 | 4 | 8 | 7 | 5 | 8 | 7 | 3 | 4 | 5 | 6.5 | 7 | 8 | 6.5 | |
| 55 - The Battle with Namor | ReworkPursuitDesign is broken — a load-bearing lens isn’t doing its job yet. | BrokenThe underlying story machine isn’t holding — worth looking at before polish. | 6.5 | 9 / 8 | 7 / 8 | 7 | 7 | 4.5 | 5 | 1 | 4 | 7 | 8 | 7 | 7.5 | 7 | 4 | 4 | 5 | 6.5 | 7.5 | 8 | 6 | |
| 56 - The Black Panther vs. Namor | PolishPursuitNo lens is broken, but Design, Execution and Read are soft — this reads as a polish pass. | SoftThe structure works but is leaking power in places. | 6.8 | 6.5 / 7.5 | 8.5 / 7.5 | 8 | 7 | 7 | 7 | 7.5 | 8 | 9 | 9 | 7 | 9 | 9 | 7 | 7 | 6 | 7.5 | 6.5 | 7 | 6.5 | |
| 57 - Ambush and Capture of Namor | ReworkPursuitDesign is broken — a load-bearing lens isn’t doing its job yet. | BrokenThe underlying story machine isn’t holding — worth looking at before polish. | 6.5 | 5.5 / 7 | 8 / 7.5 | 8 | 7 | 7 | 6 | 4 | 7 | 8 | 9 | 9 | 9 | 8 | 8 | 6 | 6 | 7 | 6 | 4 | 6.5 | |
| 58 - Midnight Angels Strike Back | KeepContestAll three lenses are solid — worth protecting as it stands. | SolidThe story machine is built and mostly working. | 6.5 | 7 / 7.5 | 8 / 7.5 | 7 | 6 | 5.5 | 6 | 3 | 5 | 8 | 9 | 9 | 9 | 7 | 5 | 6 | 6 | 7 | 6 | 6 | 6.5 | |
| 59 - The Battle For Survival | PolishContestNo lens is broken, but Design, Execution and Read are soft — this reads as a polish pass. | SoftThe structure works but is leaking power in places. | 6.5 | 7 / 7.5 | 8.5 / 7.5 | 7 | 6 | 7 | 7 | 4 | 7 | 9 | 9 | 8 | 8 | 8 | 7 | 6 | 5 | 7 | 6.5 | 7 | 6 | |
| 60 - The Battle for Wakanda | PolishContestNo lens is broken, but Design, Execution and Read are soft — this reads as a polish pass. | SoftThe structure works but is leaking power in places. | 6.5 | 7 / 7 | 8 / 7.5 | 7 | 6 | 6 | 7 | 5 | 6 | 8 | 8 | 7 | 8 | 7 | 6 | 7 | 6 | 7 | 6 | 7 | 5.5 | |
| 61 - Confrontation and Yield | KeepDeliveryAll three lenses are solid — worth protecting as it stands. | SolidThe story machine is built and mostly working. | 7.2 | 9 / 8.5 | 6.5 / 7 | 8 | 7 | 7 | 8 | 7 | 8 | 9 | 7 | 4 | 8.5 | 8 | 8 | 8 | 7 | 8 | 7.5 | 8.5 | 7 | |
| 62 - Val confronts Ross | KeepDeliveryAll three lenses are solid — worth protecting as it stands. | SolidThe story machine is built and mostly working. | 6.5 | 9 / 8.5 | 8 / 7.5 | 7 | 6 | 6.5 | 7 | 4 | 6 | 7 | 7 | 8 | 7 | 8 | 8 | 6 | 6 | 7 | 7 | 9 | 7 | |
| 63 - Van Attack and Namor's Lair | ReworkDeliveryDesign is broken — a load-bearing lens isn’t doing its job yet. | BrokenThe underlying story machine isn’t holding — worth looking at before polish. | 6.5 | 9 / 8.5 | 7 / 7.5 | 7 | 7 | 5.5 | 6 | 2 | 4 | 8 | 6 | 3 | 6 | 7 | 6 | 6 | 6 | 6.5 | 7 | 8 | 7 | |
| 64 - Repentance and Redemption | PolishAftermathNo lens is broken, but Design and Read are soft — this reads as a polish pass. | SoftThe structure works but is leaking power in places. | 6.5 | 9 / 8 | 3 / 6 | 7 | 6 | 6.5 | 8 | 5 | 7 | 8 | 3 | 2 | 3 | 5 | 5 | 7 | 7 | 6 | 6.5 | 8 | 5.5 | |
| 65 - The Throne Challenge | PolishRitualNo lens is broken, but Design and Read are soft — this reads as a polish pass. | SoftThe structure works but is leaking power in places. | 6.5 | 9 / 8 | 5 / 7 | 7 | 6 | 6 | 7 | 3 | 5 | 8 | 3 | 1 | 3 | 7 | 7 | 4 | 6 | 6.5 | 7.5 | 8 | 7 | |
| 66 - Farewell and New Beginnings | KeepDeliveryAll three lenses are solid — worth protecting as it stands. | SolidThe story machine is built and mostly working. | 8.2 | 9 / 9 | 8 / 8.5 | 9 | 8 | 7.5 | 9 | 8 | 8.5 | 6 | 4 | 2 | 6 | 8.5 | 9 | 9 | 8 | 8.5 | 8 | 9 | 8 | |
| 67 - Family Secrets Revealed | PolishDeliveryNo lens is broken, but Design and Read are soft — this reads as a polish pass. | SoftThe structure works but is leaking power in places. | 8.2 | 9.5 / 9 | 7.5 / 8 | 9 | 8 | 7 | 9 | 8 | 9 | 8 | 3 | 2 | 6 | 7 | 9 | 10 | 8 | 9 | 8 | 9 | 8.5 | |
“Grab ‘em by the throat and never let ‘em go.”
The scene level score is the impact on the reader or audience to continue reading.
The Script score is how compelled they are to keep reading based on the rest of the script so far.
The scene ends with a devastating emotional cliffhanger (T'Challa's death) that compels the reader to see how the story proceeds without him.
Given the whole script so far (only this scene), the death of the main hero creates a massive hook and unresolved questions about the future of Wakanda and Shuri's arc, strongly pulling the reader forward.
“Grab ‘em by the throat and never let ‘em go.”
The scene level score is the impact on the reader or audience to continue reading.
The Script score is how compelled they are to keep reading based on the rest of the script so far.
The scene compels continuation by ending with a time jump and the promise of new storylines (the UN hearing, the Mali attack), but the funeral itself feels self-contained and does not end on a cliffhanger.
Given the whole script so far, the reader is pulled to continue by the unresolved threads from the previous scene (Shuri's failed attempt to save T'Challa) and the new hooks (Ramonda at the UN, the mercenary attack), though this scene slows momentum.
“Grab ‘em by the throat and never let ‘em go.”
The scene level score is the impact on the reader or audience to continue reading.
The Script score is how compelled they are to keep reading based on the rest of the script so far.
The scene ends with Ramonda's defiant speech, which creates a sense of resolve but no cliffhanger or open question—it feels self-contained, so the reader may not feel urgent need to continue.
Given the script so far, the funeral's emotional weight and Shuri's grief create strong momentum, but this scene shifts to a colder political register that slows that momentum. The unresolved threads (Shuri's grief, the herb's failure, global threats) still pull the reader forward, but less urgently.
“Grab ‘em by the throat and never let ‘em go.”
The scene level score is the impact on the reader or audience to continue reading.
The Script score is how compelled they are to keep reading based on the rest of the script so far.
The scene ends with a new mystery (the vibranium discovery) and a lingering threat (the U.S. Secretary's reaction), compelling the reader to see what happens next. The deep-sea mining setup creates a strong hook.
The script so far has established T'Challa's death, Shuri's grief, and now Wakanda's political and military response. The deep-sea mining thread adds a new global conflict, while Ramonda's warning suggests future attacks. The momentum is strong, though the tonal shift from grief to action may feel jarring.
“Grab ‘em by the throat and never let ‘em go.”
The scene level score is the impact on the reader or audience to continue reading.
The Script score is how compelled they are to keep reading based on the rest of the script so far.
The scene ends on a strong cliffhanger with the loss of both divers and a new threat on the surface, creating a clear open question about what the creature is and what happens next, compelling the reader to continue.
The script has built momentum through political intrigue, Wakanda's defensive actions, and now a mysterious underwater threat. The vibranium discovery and the attack add a new, dangerous layer to the global conflict, maintaining strong cumulative interest.
“Grab ‘em by the throat and never let ‘em go.”
The scene level score is the impact on the reader or audience to continue reading.
The Script score is how compelled they are to keep reading based on the rest of the script so far.
This scene ends on a cliffhanger (helicopter escape, Talocanil still present) and introduces a major new threat, making the reader want to see what happens next to Dr. Graham and how the Talocanil will be confronted.
The script has built momentum through the UN hearing, the Dora Milaje action, and the vibranium discovery. This scene introduces a powerful new antagonist faction, raising the stakes and opening new story threads, compelling the reader to continue.
“Grab ‘em by the throat and never let ‘em go.”
The scene level score is the impact on the reader or audience to continue reading.
The Script score is how compelled they are to keep reading based on the rest of the script so far.
The scene ends with a cliffhanger (helicopter dragged underwater, ship exploding) and the introduction of Namor, creating strong suspense. The reader wants to know what happens to Dr. Graham and what Namor's plan is, compelling them to continue.
The script has built momentum through the UN political drama, the Dora Milaje action, and the CIA investigation. This scene introduces a major new threat (Talocanil) that raises the stakes for Wakanda and the world, making the reader eager to see how Ramonda and Shuri will respond.
“Grab ‘em by the throat and never let ‘em go.”
The scene level score is the impact on the reader or audience to continue reading.
The Script score is how compelled they are to keep reading based on the rest of the script so far.
The scene ends with Shuri agreeing to go with Ramonda, creating mild curiosity about where they're going, but it's a soft cliffhanger that doesn't urgently demand the next scene.
Given the script so far, the unresolved threats (Namor, vibranium theft, global tensions) and Shuri's emotional arc create momentum, but this scene is a breather that slows the pace without adding new plot hooks.
“Grab ‘em by the throat and never let ‘em go.”
The scene level score is the impact on the reader or audience to continue reading.
The Script score is how compelled they are to keep reading based on the rest of the script so far.
The scene ends on a note of emotional openness—Shuri has confessed her rage, and Ramonda offers compassion. This creates a desire to see what Shuri will do next: will she burn the clothes? Will she begin to heal? The scene compels continuation.
Given the whole script so far, the unresolved external conflicts (Namor, the UN, the search for vibranium) are still active, but this scene deepens the emotional core. The reader is pulled forward by both the external plot and the need to see Shuri's character arc resolve.
“Grab ‘em by the throat and never let ‘em go.”
The scene level score is the impact on the reader or audience to continue reading.
The Script score is how compelled they are to keep reading based on the rest of the script so far.
This scene compels the reader to continue because it ends with a major cliffhanger (the vibranium detector by the fire) and raises urgent questions: Will Wakanda help Namor? Who is the scientist? What will happen next?
Given the whole script so far, the reader is strongly compelled to continue because the story has built multiple threads: Shuri's grief, Wakanda's political struggles, the underwater vibranium threat, and Namor's mysterious civilization. The momentum is high, and the scene adds a new, powerful antagonist.
“Grab ‘em by the throat and never let ‘em go.”
The scene level score is the impact on the reader or audience to continue reading.
The Script score is how compelled they are to keep reading based on the rest of the script so far.
The scene ends with Ramonda considering M'Baku's point, leaving the council's decision unresolved. This creates a moderate hook—readers want to know what they decide—but the scene feels self-contained as a debate.
The script so far has built strong momentum with Namor's introduction, the UN confrontation, and the underwater attack. This council scene maintains that momentum by deepening the political stakes, though it slows the pace slightly. The unresolved threat and Ramonda's leadership arc keep the reader invested.
“Grab ‘em by the throat and never let ‘em go.”
The scene level score is the impact on the reader or audience to continue reading.
The Script score is how compelled they are to keep reading based on the rest of the script so far.
This scene compels the reader to continue because it sets up a clear mission (find the scientist) and introduces a new character (the unknown inventor), creating curiosity about who they are and how they'll be found.
Given the whole script so far, the reader is pulled forward by the unresolved threat of Namor, the mystery of the scientist, and Shuri's emotional arc. This scene adds a new thread (the mission) but doesn't escalate existing tensions, so momentum holds steady.
“Grab ‘em by the throat and never let ‘em go.”
The scene level score is the impact on the reader or audience to continue reading.
The Script score is how compelled they are to keep reading based on the rest of the script so far.
The scene ends with Riri's shocked 'WHAT?!' after hearing about Namor, creating a strong cliffhanger that compels the reader to see her reaction and whether she agrees to go to Wakanda.
The script has strong cumulative momentum: the Namor threat is escalating, Shuri's grief arc is simmering, and now a new character with high stakes is introduced. The playful tone here provides a necessary breather, but the overall tension remains high.
“Grab ‘em by the throat and never let ‘em go.”
The scene level score is the impact on the reader or audience to continue reading.
The Script score is how compelled they are to keep reading based on the rest of the script so far.
The scene ends on a cliffhanger with Shuri dropping the Kimoyo bead, leaving the reader wondering how they'll escape. The immediate threat of the Feds and the unresolved question of Ross's betrayal compel the reader to continue.
The script has multiple open threads: the mission to find the scientist, Namor's threat, and the political fallout from the UN. This scene adds a new layer of urgency, and the characters' dynamics are engaging, keeping the reader invested in the overall story.
“Grab ‘em by the throat and never let ‘em go.”
The scene level score is the impact on the reader or audience to continue reading.
The Script score is how compelled they are to keep reading based on the rest of the script so far.
This scene compels continuation because it ends mid-escape with the Barracuda crashing out, leaving the chase unresolved and Riri airborne—creating immediate suspense.
Given the whole script, the momentum is strong: Namor's threat, the FBI pursuit, and Riri's introduction all converge. The escape raises stakes and promises more action, keeping the reader invested.
“Grab ‘em by the throat and never let ‘em go.”
The scene level score is the impact on the reader or audience to continue reading.
The Script score is how compelled they are to keep reading based on the rest of the script so far.
The scene ends with Okoye asking 'Shuri, where are you?' which creates a mild cliffhanger about their reunion. The action is unresolved, making the reader want to see how they regroup.
Given the whole script, the chase is a high-energy interlude but doesn't advance the main Namor plot. The unresolved threat of Namor and the need to protect Riri keep the reader invested, but the action here feels like a detour.
“Grab ‘em by the throat and never let ‘em go.”
The scene level score is the impact on the reader or audience to continue reading.
The Script score is how compelled they are to keep reading based on the rest of the script so far.
This scene ends on a cliffhanger with the drone and Riri's altitude issue unresolved, and Shuri still being chased. The reader will want to see if Riri can reach the drone and if the escape succeeds.
The script has strong momentum from the UN hearing, the Mali raid, the Namor introduction, and now the FBI chase. The unresolved threats (Namor, the drone, the FBI) and the character dynamics (Shuri's grief, Okoye's duty) keep the reader invested.
“Grab ‘em by the throat and never let ‘em go.”
The scene level score is the impact on the reader or audience to continue reading.
The Script score is how compelled they are to keep reading based on the rest of the script so far.
This scene compels the reader to continue because the escape is not yet complete—the blockade is cleared but the characters are still in danger, and the next scene likely shows their extraction or further pursuit.
Given the whole script so far, the reader is pulled to continue because the Namor threat remains unresolved, Riri's role is still developing, and the chase sequence has built strong momentum. The action is satisfying but the larger plot questions (what does Namor want? how will Wakanda respond?) keep the reader invested.
“Grab ‘em by the throat and never let ‘em go.”
The scene level score is the impact on the reader or audience to continue reading.
The Script score is how compelled they are to keep reading based on the rest of the script so far.
The scene ends with Shuri and Riri captured, Okoye swept away, and a clear cliffhanger—what will Namor do? This strongly compels the reader to continue to the next scene.
Given the whole script so far, the capture of Shuri and Riri raises the stakes and promises a confrontation with Namor, while Okoye's fate is uncertain. The momentum is strong, with multiple threads (vibranium detector, Talocanil threat, Shuri's grief) converging.
“Grab ‘em by the throat and never let ‘em go.”
The scene level score is the impact on the reader or audience to continue reading.
The Script score is how compelled they are to keep reading based on the rest of the script so far.
The scene compels continuation by ending with a clear hook: Ross has the bracelet, Val is taking him on a road trip, and the audience wants to see what he does with it and how the investigation unfolds.
Given the whole script, the momentum is strong: the capture of Shuri and Riri, the introduction of Namor, and now Ross's secret possession of the bracelet create multiple threads that pull the reader forward. The scene maintains but doesn't dramatically increase this momentum.
“Grab ‘em by the throat and never let ‘em go.”
The scene level score is the impact on the reader or audience to continue reading.
The Script score is how compelled they are to keep reading based on the rest of the script so far.
The scene ends with a clear emotional cliffhanger—Okoye's dismissal and Ayo's promotion—and the unresolved fate of Shuri, compelling the reader to see how Okoye will respond and what happens next.
The script has strong momentum from the abduction and the political fallout, with multiple threads (Shuri's capture, Okoye's disgrace, Namor's threat) converging, keeping the reader invested in the cumulative story.
“Grab ‘em by the throat and never let ‘em go.”
The scene level score is the impact on the reader or audience to continue reading.
The Script score is how compelled they are to keep reading based on the rest of the script so far.
The scene ends with Ross calling Ramonda, which creates a clear hook: what will they discuss? How will Ross help? The reader wants to see the next scene to learn the plan.
The script has strong momentum from the bridge attack and the capture of Shuri and Riri. This scene maintains that momentum by introducing a new ally (Ross) and a new threat (Val). The threads of the rescue and the CIA pursuit are both active, pulling the reader forward.
“Grab ‘em by the throat and never let ‘em go.”
The scene level score is the impact on the reader or audience to continue reading.
The Script score is how compelled they are to keep reading based on the rest of the script so far.
The scene compels continuation through the conch ritual cliffhanger—readers want to see what happens when Ramonda blows the shell. The open question of whether Namor will respond drives momentum.
The script maintains strong momentum through the abduction of Shuri and Riri, the political fallout, and now the conch ritual. The threads of Ross's loyalty, the laptop encryption, and Namor's threat are all active, keeping the reader invested.
“Grab ‘em by the throat and never let ‘em go.”
The scene level score is the impact on the reader or audience to continue reading.
The Script score is how compelled they are to keep reading based on the rest of the script so far.
The scene ends with a clear hook: Ramonda is going to find Nakia, setting up a rescue mission. The open question of whether she can succeed and the two-day deadline compel the reader to continue.
The script has built strong momentum through the abduction of Shuri and Riri, the stripping of Okoye's rank, and now Ramonda's desperate gambit. The threads of the CIA investigation, the laptop encryption, and Nakia's return all pull the reader forward.
“Grab ‘em by the throat and never let ‘em go.”
The scene level score is the impact on the reader or audience to continue reading.
The Script score is how compelled they are to keep reading based on the rest of the script so far.
The scene ends with Nakia's commitment and the reveal of Talocan, creating a clear hook for the next scene (the Mayan Elder encounter). The reader wants to see how Nakia's search unfolds.
The script has strong momentum from Shuri's abduction and Okoye's fall, and this scene provides a necessary emotional reset. The threads of Ramonda's grief, Nakia's return, and the Talocan threat are all gaining steam, keeping the reader invested.
“Grab ‘em by the throat and never let ‘em go.”
The scene level score is the impact on the reader or audience to continue reading.
The Script score is how compelled they are to keep reading based on the rest of the script so far.
The scene ends with a clear hook: Shuri is led to meet Namor, leaving Riri alone. The reader wants to see what Namor wants and how Shuri will handle the cultural confrontation.
The script has strong cumulative momentum: Shuri's capture, Ramonda's deal with Namor, Nakia's mission, and now the captive scene. The threads are converging, and the reader is invested in Shuri's fate and the looming war.
“Grab ‘em by the throat and never let ‘em go.”
The scene level score is the impact on the reader or audience to continue reading.
The Script score is how compelled they are to keep reading based on the rest of the script so far.
The scene ends on a flashback cliffhanger, making the reader want to see the full origin story, but the present-tense plot is paused, reducing urgency.
Given the whole script, the abduction of Shuri and Riri, the political fallout, and Nakia's mission create strong cumulative momentum. This scene provides necessary context but slows the pace.
“Grab ‘em by the throat and never let ‘em go.”
The scene level score is the impact on the reader or audience to continue reading.
The Script score is how compelled they are to keep reading based on the rest of the script so far.
The scene ends with Namor becoming king, which feels like a natural endpoint. It doesn't create a cliffhanger or open question for the next scene, but it does deepen the reader's understanding of Namor's motivations, making future conflicts more resonant.
Given the whole script so far, this origin flashback provides crucial context for Namor's present-day actions, but it slows the momentum of the chase/rescue plot. The reader is pulled forward by the unresolved fate of Shuri and Riri, not by this scene itself.
“Grab ‘em by the throat and never let ‘em go.”
The scene level score is the impact on the reader or audience to continue reading.
The Script score is how compelled they are to keep reading based on the rest of the script so far.
The scene ends with Shuri and Namor descending into the ocean, creating a strong cliffhanger—what will Talocan look like? The reader wants to see the underwater world and learn what happens next. The open question of Riri's fate also compels continuation.
The script has built strong momentum through the chase, the attack on the bridge, and the political fallout. This scene deepens the antagonist and raises the stakes, making the reader invested in the ideological conflict. The unresolved threads (Riri's laptop, Ross's involvement, Nakia's mission) all pull forward.
“Grab ‘em by the throat and never let ‘em go.”
The scene level score is the impact on the reader or audience to continue reading.
The Script score is how compelled they are to keep reading based on the rest of the script so far.
The scene ends with a cut to Ross's chloroform attack, which creates a cliffhanger but feels disconnected from the main plot. The reader may want to see what happens to Ross, but the Talocan thread is left unresolved.
The script has built strong momentum through the action and political intrigue. This scene adds depth to Namor and Talocan, but the Ross subplot feels like a detour. The reader is still compelled by Shuri's fate and the diplomatic stakes.
“Grab ‘em by the throat and never let ‘em go.”
The scene level score is the impact on the reader or audience to continue reading.
The Script score is how compelled they are to keep reading based on the rest of the script so far.
This scene compels continuation because it ends on a cliffhanger (the guard's look), leaving the reader wondering if Ross's cover will be blown, but the cut is abrupt.
Given the whole script, the reader is pulled to continue because of the ongoing rescue mission for Shuri and Riri, the unresolved threat from Namor, and Ross's risky infiltration; this scene adds a new thread but doesn't resolve existing ones.
“Grab ‘em by the throat and never let ‘em go.”
The scene level score is the impact on the reader or audience to continue reading.
The Script score is how compelled they are to keep reading based on the rest of the script so far.
The scene ends with Ross flushing the beads and planning the next step, creating a clear hook: will he successfully swap the laptop? The open question of the laptop's fate compels the reader to continue.
The script has strong momentum: Shuri is captured, Ramonda is desperate, and Ross is actively helping. This scene reinforces the alliance and advances the plan, keeping the reader invested in the rescue mission.
“Grab ‘em by the throat and never let ‘em go.”
The scene level score is the impact on the reader or audience to continue reading.
The Script score is how compelled they are to keep reading based on the rest of the script so far.
The scene ends with the plan in motion and Nakia's approach, creating clear suspense about whether Shuri's ruse will succeed and if Nakia will reach her in time.
Given the whole script, the momentum is strong: Shuri's escape plan, Nakia's infiltration, and Ramonda's confrontation with Namor all converge, keeping the reader invested in the multiple threads.
“Grab ‘em by the throat and never let ‘em go.”
The scene level score is the impact on the reader or audience to continue reading.
The Script score is how compelled they are to keep reading based on the rest of the script so far.
This scene compels the reader to continue because it ends with Namor's ultimatum and Ramonda's failed negotiation, leaving open questions: Will Shuri accept the alliance? Will Ramonda find another way? The suspense is moderate but clear.
Given the whole script, the reader is pulled forward by the unresolved arcs: Shuri's captivity, the scientist's fate, Ross's covert mission, and Nakia's search. The scene maintains momentum but the repetitive negotiation slightly cools the urgency built earlier.
“Grab ‘em by the throat and never let ‘em go.”
The scene level score is the impact on the reader or audience to continue reading.
The Script score is how compelled they are to keep reading based on the rest of the script so far.
This scene compels the reader to continue because the failed rescue and the killing of the guards create immediate consequences: war is now inevitable, and Shuri's moral stance is challenged. The reader wants to see how this escalates.
Given the whole script so far, the reader is pulled to continue because the stakes have been raised dramatically: Shuri is still captive, war looms, and the rescue attempt has failed. The momentum from previous scenes (Ramonda's deal, Nakia's infiltration) builds to this crisis point.
“Grab ‘em by the throat and never let ‘em go.”
The scene level score is the impact on the reader or audience to continue reading.
The Script score is how compelled they are to keep reading based on the rest of the script so far.
This scene compels continuation through the unresolved threat of Namor's retaliation and the mystery of Okoye's demotion, but the self-contained rescue resolution slightly reduces urgency.
The script maintains strong momentum through the accumulated arcs of Shuri's captivity, Namor's threat, and the political fallout in Wakanda; this scene adds a new thread (Okoye's demotion) while resolving the rescue, keeping the reader invested.
“Grab ‘em by the throat and never let ‘em go.”
The scene level score is the impact on the reader or audience to continue reading.
The Script score is how compelled they are to keep reading based on the rest of the script so far.
This scene compels continuation by ending on a clear cliffhanger—Namor's war plan—leaving the reader eager to see the attack on Wakanda.
Given the whole script, the momentum is strong: Shuri's escape, Nakia's involvement, and now Namor's retaliation create multiple threads that pull the reader forward.
“Grab ‘em by the throat and never let ‘em go.”
The scene level score is the impact on the reader or audience to continue reading.
The Script score is how compelled they are to keep reading based on the rest of the script so far.
This scene compels continuation through the looming threat of Namor and the unresolved bracelet symbol, but the fragmented structure slightly dampens urgency.
Given the whole script, the accumulated momentum from Namor's betrayal and Shuri's escape keeps the reader invested, though this scene's slower pace provides a breather that risks losing tension.
“Grab ‘em by the throat and never let ‘em go.”
The scene level score is the impact on the reader or audience to continue reading.
The Script score is how compelled they are to keep reading based on the rest of the script so far.
The scene compels continuation because the flood raises immediate questions about the attack's source and scale, but the self-contained dialogue moment slightly reduces urgency.
Given the whole script, the reader is pulled forward by the unresolved threat of Namor's retaliation and the emotional arcs of Okoye and Nakia, though the pacing here is a minor drag.
“Grab ‘em by the throat and never let ‘em go.”
The scene level score is the impact on the reader or audience to continue reading.
The Script score is how compelled they are to keep reading based on the rest of the script so far.
This scene compels continuation due to the unresolved attack and cliffhanger of the sirens, but the fragmented structure slightly reduces urgency.
Given the whole script, the attack on Wakanda raises stakes and hooks the reader, but the cumulative momentum is slightly slowed by the scene's disjointed nature.
“Grab ‘em by the throat and never let ‘em go.”
The scene level score is the impact on the reader or audience to continue reading.
The Script score is how compelled they are to keep reading based on the rest of the script so far.
This scene compels the reader to continue because the attack is unresolved, Namor is advancing on the palace, and multiple characters are in peril, creating strong cliffhangers.
Given the whole script, the attack on Wakanda is a major escalation that pays off the buildup of Talocan as a threat; the reader is pulled forward by the need to see the outcome and the fates of key characters like Shuri and Ramonda.
“Grab ‘em by the throat and never let ‘em go.”
The scene level score is the impact on the reader or audience to continue reading.
The Script score is how compelled they are to keep reading based on the rest of the script so far.
This scene ends on a cliffhanger with Namor attacking the Tribal Council windows, Ramonda and Riri in danger, and Shuri's fate uncertain, compelling the reader to continue.
The script has built strong momentum with the invasion, character arcs (Shuri's growth, Ramonda's leadership), and unresolved conflicts (Namor's threat, Riri's safety), making the reader eager to see the resolution.
“Grab ‘em by the throat and never let ‘em go.”
The scene level score is the impact on the reader or audience to continue reading.
The Script score is how compelled they are to keep reading based on the rest of the script so far.
This scene creates a massive cliffhanger with the death of the queen and Namor's one-week ultimatum. The reader is compelled to immediately see the aftermath and how Shuri will respond to this devastating loss.
The script has built immense momentum. The attack on Wakanda and the death of Ramonda are the culmination of the central conflict. The reader is now deeply invested in Shuri's journey of grief and vengeance, and the promise of a final confrontation with Namor is a powerful hook.
“Grab ‘em by the throat and never let ‘em go.”
The scene level score is the impact on the reader or audience to continue reading.
The Script score is how compelled they are to keep reading based on the rest of the script so far.
The scene ends with Shuri in Nakia's arms, a moment of fragile hope. It compels the reader to continue because Shuri's emotional state is still precarious, and the funeral scene (207) is clearly next, promising further exploration of her grief.
Given the whole script, the reader is pulled forward by the unresolved war with Talocan, Ramonda's death, and Shuri's now-fragile will to live. This scene deepens the emotional stakes, making the coming confrontation with Namor more resonant. The momentum is strong.
“Grab ‘em by the throat and never let ‘em go.”
The scene level score is the impact on the reader or audience to continue reading.
The Script score is how compelled they are to keep reading based on the rest of the script so far.
The scene ends with Shuri's declaration of vengeance, which creates a clear hook for the next scene (how will she pursue it?), but the scene itself is self-contained.
The script has strong momentum from the attack and Ramonda's death, and this scene deepens Shuri's character arc, maintaining reader investment in her journey.
“Grab ‘em by the throat and never let ‘em go.”
The scene level score is the impact on the reader or audience to continue reading.
The Script score is how compelled they are to keep reading based on the rest of the script so far.
The scene ends with the elders thinking, which is a soft pause. It doesn't create a strong cliffhanger, but the unresolved political tension and the mention of Shuri working on new technology create mild curiosity about what happens next.
Given the whole script, the momentum is still strong from the attack and Ramonda's death. The political infighting adds a new layer of tension, but the scene itself doesn't accelerate the plot significantly. The reader is likely to continue out of investment in the larger story rather than this scene's hook.
“Grab ‘em by the throat and never let ‘em go.”
The scene level score is the impact on the reader or audience to continue reading.
The Script score is how compelled they are to keep reading based on the rest of the script so far.
The scene ends with a clear hook—Ross must now deal with the CIA—but it feels self-contained and doesn't create a strong cliffhanger.
Given the whole script, the death of Ramonda and Shuri's new resolve are major threads, but this scene is a brief update that doesn't add much momentum.
“Grab ‘em by the throat and never let ‘em go.”
The scene level score is the impact on the reader or audience to continue reading.
The Script score is how compelled they are to keep reading based on the rest of the script so far.
The scene ends with Ross walking back to the building, leaving the reader wondering if he'll be able to delay the attack, creating suspense.
Given the whole script, the U.S. threat adds a new layer of danger on top of Namor's attack, keeping momentum high and pulling the reader forward.
“Grab ‘em by the throat and never let ‘em go.”
The scene level score is the impact on the reader or audience to continue reading.
The Script score is how compelled they are to keep reading based on the rest of the script so far.
The scene ends with Shuri declaring 'Immediately,' creating a strong hook that makes the reader want to see the results of her work and the coming battle. The open question of whether she will succeed in becoming the Black Panther drives continuation.
Given the entire script, the momentum is high: Ramonda's death, Shuri's grief, and the threat of Namor's attack have built significant stakes. This scene channels that momentum into preparation, keeping the reader invested in the resolution.
“Grab ‘em by the throat and never let ‘em go.”
The scene level score is the impact on the reader or audience to continue reading.
The Script score is how compelled they are to keep reading based on the rest of the script so far.
The scene ends with Shuri awakening underwater in the Ancestral Plane, a strong cliffhanger that compels the reader to continue to see what happens next.
Given the script's momentum—Shuri's transformation, the unresolved threat of Namor, and the political tensions—this scene raises the stakes and deepens character investment, strongly pulling the reader forward.
“Grab ‘em by the throat and never let ‘em go.”
The scene level score is the impact on the reader or audience to continue reading.
The Script score is how compelled they are to keep reading based on the rest of the script so far.
The scene ends with Shuri's vow to kill Namor, creating a strong cliffhanger about whether she will succeed and what she will become. The reader is compelled to see the consequences.
The script has built significant momentum through the attack on Wakanda and Ramonda's death. This scene deepens Shuri's character arc and raises the stakes for the final act, keeping the reader invested.
“Grab ‘em by the throat and never let ‘em go.”
The scene level score is the impact on the reader or audience to continue reading.
The Script score is how compelled they are to keep reading based on the rest of the script so far.
The scene ends on a triumphant note with the elders cheering, which provides closure but also sets up the next phase of the story (Shuri as Black Panther). The reader is compelled to continue to see how she will use her new role against Namor.
Given the whole script, the momentum is strong: Shuri has just become the Black Panther, the conflict with Namor is unresolved, and the fate of Wakanda hangs in the balance. The scene reinforces the central arc and raises anticipation for the final confrontation.
“Grab ‘em by the throat and never let ‘em go.”
The scene level score is the impact on the reader or audience to continue reading.
The Script score is how compelled they are to keep reading based on the rest of the script so far.
The scene ends with Shuri walking out, leaving the plan in motion and the moral question unresolved. This creates a strong hook to see if she will follow through and how M'Baku's argument will affect her.
The script has built significant momentum through the attack, Ramonda's death, and Shuri's transformation. This scene deepens the philosophical stakes and keeps the reader invested in Shuri's journey and the coming confrontation.
“Grab ‘em by the throat and never let ‘em go.”
The scene level score is the impact on the reader or audience to continue reading.
The Script score is how compelled they are to keep reading based on the rest of the script so far.
This scene compels the reader to continue because the ambush has just begun, and the outcome is unresolved—Namor is under attack but not defeated, creating immediate suspense.
Given the whole script, the reader is pulled to continue because the final confrontation with Namor is now underway, and Shuri's internal conflict (vengeance vs. protection) remains unresolved. The momentum from the previous scenes (Ramonda's death, Shuri's transformation) carries forward, though this scene itself adds little new emotional fuel.
“Grab ‘em by the throat and never let ‘em go.”
The scene level score is the impact on the reader or audience to continue reading.
The Script score is how compelled they are to keep reading based on the rest of the script so far.
This scene compels the reader to continue because it ends with Namor flying up with a conch shell, an action that clearly sets up his next move. The open question is what he will do with it, creating suspense for the next scene.
Given the whole script, the reader is pulled to continue because the battle is escalating, Shuri's plan is in motion, and Namor's counterattack is imminent. The momentum from previous scenes (the ambush setup, Shuri's transformation) carries forward strongly.
“Grab ‘em by the throat and never let ‘em go.”
The scene level score is the impact on the reader or audience to continue reading.
The Script score is how compelled they are to keep reading based on the rest of the script so far.
The scene ends with Namor captured, creating a strong cliffhanger about what will happen next, compelling the reader to continue.
Given the whole script, the capture of Namor is a major payoff, but the unresolved philosophical conflict and Shuri's vengeance arc keep the reader invested in the aftermath.
“Grab ‘em by the throat and never let ‘em go.”
The scene level score is the impact on the reader or audience to continue reading.
The Script score is how compelled they are to keep reading based on the rest of the script so far.
This scene compels forward with a cliffhanger: Namor is captured but the ship is damaged, and Shuri's plan is in motion. Readers want to see if the trap succeeds and how they escape the sinking ship.
Cumulatively, the script maintains strong momentum: unresolved vengeance arc, Talocan threat, Shuri's internal conflict, and the destruction of the Heart-Shaped Herb all push forward. This scene adds a raised stakes and a captured villain, which typically sustains reader investment.
“Grab ‘em by the throat and never let ‘em go.”
The scene level score is the impact on the reader or audience to continue reading.
The Script score is how compelled they are to keep reading based on the rest of the script so far.
This scene compels continuation because the ship is still in danger and the Midnight Angels have just arrived, creating a cliffhanger. The reader wants to see if the rescue succeeds.
Given the whole script, the momentum is strong with the climactic battle and unresolved character arcs (Shuri's vengeance, Okoye's redemption). This scene maintains that momentum, though the technical focus slightly dampens emotional investment.
“Grab ‘em by the throat and never let ‘em go.”
The scene level score is the impact on the reader or audience to continue reading.
The Script score is how compelled they are to keep reading based on the rest of the script so far.
The scene ends with the duel unresolved and the ship battle ongoing, creating strong cliffhangers that compel the reader to continue.
The script maintains momentum through multiple concurrent threads (Shuri vs. Namor, ship battle, Midnight Angels), and the unresolved climax keeps the reader invested.
“Grab ‘em by the throat and never let ‘em go.”
The scene level score is the impact on the reader or audience to continue reading.
The Script score is how compelled they are to keep reading based on the rest of the script so far.
The scene ends with Shuri pursuing Namor and Okoye showing mercy, leaving open questions about the final outcome and the Talocanil threat, compelling the reader to continue.
Given the whole script, the accumulated momentum of Shuri's journey and the unresolved war with Talocanil strongly pull the reader forward, though the intercutting slightly dampens the drive.
“Grab ‘em by the throat and never let ‘em go.”
The scene level score is the impact on the reader or audience to continue reading.
The Script score is how compelled they are to keep reading based on the rest of the script so far.
The scene resolves the central conflict, so there is no cliffhanger—but the final threat ('I will find and kill you') creates a lingering tension that makes the reader curious about the aftermath and the new alliance.
Given the whole script, the reader is pulled forward by the need to see the aftermath of the alliance, the fate of the characters (especially Ross and Val), and whether Shuri's choice will hold. The momentum is strong but slightly diminished by the clean resolution.
“Grab ‘em by the throat and never let ‘em go.”
The scene level score is the impact on the reader or audience to continue reading.
The Script score is how compelled they are to keep reading based on the rest of the script so far.
The scene ends with Ross being arrested and sirens approaching, creating a strong cliffhanger that makes the reader want to see what happens next.
Given the whole script, this scene adds a new mystery (blue-skinned attackers) and raises the stakes for Ross, maintaining momentum from the previous political and action threads.
“Grab ‘em by the throat and never let ‘em go.”
The scene level score is the impact on the reader or audience to continue reading.
The Script score is how compelled they are to keep reading based on the rest of the script so far.
The scene ends with a clear hook: Okoye says 'Let's go,' and then cuts to Namor's cave, creating curiosity about what happens next with both Ross and Namor.
Given the whole script, the rescue of Ross is a minor but welcome beat, and the cut to Namor's cave maintains momentum from the previous battle. The story still has threads about Talocan and Wakanda's future, keeping interest high.
“Grab ‘em by the throat and never let ‘em go.”
The scene level score is the impact on the reader or audience to continue reading.
The Script score is how compelled they are to keep reading based on the rest of the script so far.
This scene feels self-contained and does not create a strong hook for the next scene, as it resolves most threads and ends on a peaceful note.
Given the whole script, the reader is likely satisfied with the resolution but may be curious about Ross's fate and Val's machinations, which were set up earlier; this scene loses some momentum.
“Grab ‘em by the throat and never let ‘em go.”
The scene level score is the impact on the reader or audience to continue reading.
The Script score is how compelled they are to keep reading based on the rest of the script so far.
The scene feels self-contained and doesn't create a strong cliffhanger, but it sets up M'Baku's new role, making the reader curious about how he'll lead.
Given the script's momentum from the previous action-heavy scenes, this quieter moment provides a breather but may slow engagement; the unresolved threads with Namor and Shuri's emotional state still pull the reader forward.
“Grab ‘em by the throat and never let ‘em go.”
The scene level score is the impact on the reader or audience to continue reading.
The Script score is how compelled they are to keep reading based on the rest of the script so far.
The scene ends on a hopeful, open note, making the reader curious about Toussaint's future and Shuri's new role as aunt. It compels continuation.
The script has built strong momentum through action and political conflict, and this emotional denouement provides a satisfying payoff while opening new threads (Toussaint's destiny, Okoye's journey). The reader is invested in seeing how these threads develop.
“Grab ‘em by the throat and never let ‘em go.”
The scene level score is the impact on the reader or audience to continue reading.
The Script score is how compelled they are to keep reading based on the rest of the script so far.
This scene provides a strong emotional closure, making it feel like a natural ending point. However, the introduction of Toussaint creates curiosity about his future role, compelling the reader to continue to see how this new character will be integrated.
Given the entire script, this scene is the emotional climax of Shuri's arc and the thematic resolution. The reader is pulled to continue because the film is ending, and this scene provides a satisfying conclusion while hinting at future stories.
| Trope | Trope Details | Trope Explanation |
|---|---|---|
| Death of a Main Character | King T'Challa dies, leaving a void in Wakanda that needs to be filled | One of the most common tropes in screenwriting where a beloved character dies, which creates a sense of loss and emotional turmoil in the audience. This trope has been used in multiple movies and TV shows including Game of Thrones where multiple main characters die throughout the series. |
| Hostage Situation | Mercenaries take the Mali Outreach Center hostage, demanding access to vibranium | A plot device where a group of people are held hostage, creating a sense of urgency and danger. This trope is commonly used in crime and action thrillers, one example of which would be Die Hard where John McClane battles a group of terrorists who have taken hostages in a building |
| Secret Organization/Conspiracy | The government is suspicious of Wakanda's technology and wants to investigate it | A plot device that involves a secret organization or conspiracy, which usually works behind the scenes and operates outside the law. This trope has been used in multiple movies and TV shows including the Bourne series where the main character tries to uncover a conspiracy within the CIA. |
| Redemption Arc | Namor offers Aneka redemption | A character who initially starts off as a villain but later redeems themselves by performing a heroic act or by working to make things right. This trope is commonly used in superhero movies and TV shows, one example of which would be Loki, who starts as a villain in the Marvel Cinematic Universe but later redeems himself. |
| Revenge Plot | Shuri contemplates revenge against Namor | A plot device that involves a character seeking revenge against someone who has wronged them. This trope has been used in multiple movies and TV shows including Kill Bill where the main character seeks revenge against the people who wronged her. |
| Chosen One | Shuri and her team work on developing a new Black Panther successor | A plot device where a character is chosen to fulfill a specific destiny or mission. This trope is commonly used in fantasy and sci-fi movies and TV shows, one example of which would be Harry Potter where he is chosen to defeat Voldemort and save the wizarding world. |
| Family Reunion | Shuri meets her nephew, Prince T'Challa, and forms an emotional connection with him | A plot device where family members who have been separated from each other for a long time are reunited. This trope is commonly used in dramas and comedies, one example of which would be the movie Coco where a boy is reunited with his deceased family members during the Day of the Dead festival. |
| Scene Number | Line |
|---|---|
| 52 | M'Baku: THE BLACK PANTHER LIVES!!!! |
| 56 | Shuri: I am the spirit of a murdered queen, the wrath of a wounded nation, I am the Black Panther! And I am here for retribution. |
| 37 | Namor: We will match bloodshed with bloodshed. |
| 24 | Namor: If you try to find us...I will kill the Princess, and then I will come to Wakanda and kill you. Do you understand? |
| 5 | Dr. Graham: We lost them! GODDAMN IT. |
| Array ( [0] => Wakanda faces an imminent threat of war from Namor, and a group of military-types venture into the seas to find vibranium. [1] => Queen Ramonda takes the reins of Wakanda's vibranium policy while defending against a mercenary attack on a Mali outreach center. [2] => Shuri becomes the Black Panther again and strategizes to weaken Namor through dehydration, leading to his capture. [3] => A tragedy strikes as Wakandan forces foil attacks to safeguard their vibranium mines and the kingdom. [4] => Ross is taken into custody as Shuri nostalgically remembers T'Challa while bidding Okoye farewell. ) |
| After the death of her brother, Princess Shuri must confront a powerful underwater civilization and its leader, Namor, who threatens Wakanda and the world. |
| Grieving the loss of her family, Shuri grapples with her identity and the legacy of the Black Panther as she faces a new enemy with access to vibranium. |
| Wakanda's isolationist policies are challenged when an underwater nation emerges, forcing Shuri to decide between tradition and global engagement. |
| A young MIT student's invention leads to a clash between Wakanda and a hidden underwater civilization, forcing Shuri to become the Black Panther and protect her nation. |
| Shuri must overcome her grief and embrace the mantle of the Black Panther to prevent a devastating war between Wakanda and the underwater kingdom of Talocan. |
Got an idea to improve our service? We'd love to hear it!
Brainstorm credits pay for AI generations like Show me how to write this. They auto-refill with each new analysis. Top up here without leaving the page.
All three lenses are solid — worth protecting as it stands.
HoldingThe reader can follow what matters.
Craft Read is the familiar battery — concept, plot, characters, dialogue, stakes, pacing.
Scene Mechanics is twelve specific ways a scene stalls — it ends about where it started, nothing is really pushing it, you can call the beats before they land — with about forty finer versions underneath them. So when a scene drags, you find out what's dragging it — not just how much.
7/10 core
It commits to one clear thing and holds it
8/10 core
A real force keeps it pushing forward
5/10 expected
The surface is full of events and motion, but the governing thread ends where it started — activity substitutes for evolution. Distinct from beats literally restating the same note.
It restates its note rather than deepening it
8/10 core
It turns — something is different by the end
8/10 core
What happens here obliges what comes next
7/10 core
Every beat and line earns its place
6/10 expected
The parts are ordered and seamed so they build
9/10 core
The reader can follow what matters
4/10 light
It plays close to the version we’ve seen before
This scene's role doesn't owe this, so a low reading here is neutral rather than a fault.
3/10 light
The beats can be called before they land
This scene's role doesn't owe this, so a low reading here is neutral rather than a fault.
8/10 core
The feeling comes off the page
9/10 core
The exit pulls you into the next one
This scene has been scored but its written read hasn’t been generated yet — the notes above are derived from the scores.
“Grab ‘em by the throat and never let ‘em go.”
The scene level score is the impact on the reader or audience to continue reading.
The Script score is how compelled they are to keep reading based on the rest of the script so far.
The scene ends with a devastating emotional cliffhanger (T'Challa's death) that compels the reader to see how the story proceeds without him.
Given the whole script so far (only this scene), the death of the main hero creates a massive hook and unresolved questions about the future of Wakanda and Shuri's arc, strongly pulling the reader forward.
No lens is broken, but Design, Execution and Read are soft — this reads as a polish pass.
A ritual beat repeats a known pattern on purpose, so movement and freshness read low by design.
HoldingThe reader can follow what matters.
Craft Read is the familiar battery — concept, plot, characters, dialogue, stakes, pacing.
Scene Mechanics is twelve specific ways a scene stalls — it ends about where it started, nothing is really pushing it, you can call the beats before they land — with about forty finer versions underneath them. So when a scene drags, you find out what's dragging it — not just how much.
6/10 core
It commits to one clear thing and holds it
4/10 expected
The scene asserts tension/stakes/unease but no locatable page-visible force produces it — mood is mistaken for pressure (the pressure firewall).
It leans on mood instead of something actually pushing it
3/10 light
It restates its note rather than deepening it
This scene's role doesn't owe this, so a low reading here is neutral rather than a fault.
4/10 core
The unit connects, displays, or frames — it never attempts to change a dramatic condition. Distinct from a turn that is attempted but does not land (unclear_turn). An interlude doing its intended job is a craft choice, not this flaw.
It ends about where it started
5/10 expected
The result doesn’t oblige what comes next
5/10 expected
The scene reaches its function and keeps going, or carries beats/lines cuttable without losing what it's there to do — waste not explained by the mechanism.
There’s avoidable waste on the page
5/10 expected
The scene/sequence shifts location, time, POV, mode, or thread without making the causal/spatial/emotional/rhythmic relationship between adjacent chunks legible.
The parts sit side by side rather than building
7/10 core
The reader can follow what matters
3/10 expected
The scene's main situation/image/beat-pattern is recognizable genre convention and the script adds no specific inversion, collision, POV, cost, world-rule, or tonal twist that changes how it plays.
It plays close to the version we’ve seen before
2/10 light
The beats can be called before they land
This scene's role doesn't owe this, so a low reading here is neutral rather than a fault.
6/10 core
The feeling comes off the page
5/10 core
The unit completes its business and ends on a settled beat — no new live question, demand, or expectation is created for the next unit to inherit.
It settles at the exit rather than pulling on
This scene has been scored but its written read hasn’t been generated yet — the notes above are derived from the scores.
No explanation provided.
No explanation provided.
“Grab ‘em by the throat and never let ‘em go.”
The scene level score is the impact on the reader or audience to continue reading.
The Script score is how compelled they are to keep reading based on the rest of the script so far.
The scene compels continuation by ending with a time jump and the promise of new storylines (the UN hearing, the Mali attack), but the funeral itself feels self-contained and does not end on a cliffhanger.
Given the whole script so far, the reader is pulled to continue by the unresolved threads from the previous scene (Shuri's failed attempt to save T'Challa) and the new hooks (Ramonda at the UN, the mercenary attack), though this scene slows momentum.
All three lenses are solid — worth protecting as it stands.
HoldingThe reader can follow what matters.
Craft Read is the familiar battery — concept, plot, characters, dialogue, stakes, pacing.
Scene Mechanics is twelve specific ways a scene stalls — it ends about where it started, nothing is really pushing it, you can call the beats before they land — with about forty finer versions underneath them. So when a scene drags, you find out what's dragging it — not just how much.
7/10 core
It commits to one clear thing and holds it
7/10 core
A real force keeps it pushing forward
5/10 expected
Beats restate the same note; the reader’s experience does not change across the scene.
It restates its note rather than deepening it
6/10 core
It turns — something is different by the end
7/10 expected
What happens here obliges what comes next
6/10 expected
Every beat and line earns its place
6/10 expected
The parts are ordered and seamed so they build
8/10 core
The reader can follow what matters
5/10 light
It plays close to the version we’ve seen before
This scene's role doesn't owe this, so a low reading here is neutral rather than a fault.
4/10 light
The beats can be called before they land
This scene's role doesn't owe this, so a low reading here is neutral rather than a fault.
7/10 expected
The feeling comes off the page
7/10 core
The exit pulls you into the next one
This scene has been scored but its written read hasn’t been generated yet — the notes above are derived from the scores.
No explanation provided.
No explanation provided.
“Grab ‘em by the throat and never let ‘em go.”
The scene level score is the impact on the reader or audience to continue reading.
The Script score is how compelled they are to keep reading based on the rest of the script so far.
The scene ends with Ramonda's defiant speech, which creates a sense of resolve but no cliffhanger or open question—it feels self-contained, so the reader may not feel urgent need to continue.
Given the script so far, the funeral's emotional weight and Shuri's grief create strong momentum, but this scene shifts to a colder political register that slows that momentum. The unresolved threads (Shuri's grief, the herb's failure, global threats) still pull the reader forward, but less urgently.
All three lenses are solid — worth protecting as it stands.
HoldingThe reader can follow what matters.
Craft Read is the familiar battery — concept, plot, characters, dialogue, stakes, pacing.
Scene Mechanics is twelve specific ways a scene stalls — it ends about where it started, nothing is really pushing it, you can call the beats before they land — with about forty finer versions underneath them. So when a scene drags, you find out what's dragging it — not just how much.
7/10 core
It commits to one clear thing and holds it
7/10 core
A real force keeps it pushing forward
6/10 expected
The situation deepens as it goes
7/10 core
It turns — something is different by the end
7/10 expected
What happens here obliges what comes next
6/10 expected
Every beat and line earns its place
7/10 expected
The parts are ordered and seamed so they build
8/10 core
The reader can follow what matters
5/10 light
It plays close to the version we’ve seen before
This scene's role doesn't owe this, so a low reading here is neutral rather than a fault.
5/10 light
The beats can be called before they land
This scene's role doesn't owe this, so a low reading here is neutral rather than a fault.
7/10 expected
The feeling comes off the page
8/10 core
The exit pulls you into the next one
This scene has been scored but its written read hasn’t been generated yet — the notes above are derived from the scores.
No explanation provided.
No explanation provided.
“Grab ‘em by the throat and never let ‘em go.”
The scene level score is the impact on the reader or audience to continue reading.
The Script score is how compelled they are to keep reading based on the rest of the script so far.
The scene ends with a new mystery (the vibranium discovery) and a lingering threat (the U.S. Secretary's reaction), compelling the reader to see what happens next. The deep-sea mining setup creates a strong hook.
The script so far has established T'Challa's death, Shuri's grief, and now Wakanda's political and military response. The deep-sea mining thread adds a new global conflict, while Ramonda's warning suggests future attacks. The momentum is strong, though the tonal shift from grief to action may feel jarring.
No lens is broken, but Design, Execution and Read are soft — this reads as a polish pass.
HoldingA real force keeps it pushing forward.
Craft Read is the familiar battery — concept, plot, characters, dialogue, stakes, pacing.
Scene Mechanics is twelve specific ways a scene stalls — it ends about where it started, nothing is really pushing it, you can call the beats before they land — with about forty finer versions underneath them. So when a scene drags, you find out what's dragging it — not just how much.
4/10 core
Several candidate threads compete and none governs — the scene splits its focus rather than committing to one determinate spine.
It isn’t clearly about one thing yet
7/10 core
A real force keeps it pushing forward
5/10 expected
The surface is full of events and motion, but the governing thread ends where it started — activity substitutes for evolution. Distinct from beats literally restating the same note.
It restates its note rather than deepening it
6/10 core
The plot advances because something external happens, but the unit's own thread doesn't change state — the turn was imported, not made.
It turns — something is different by the end
7/10 expected
What happens here obliges what comes next
5/10 expected
The scene reaches its function and keeps going, or carries beats/lines cuttable without losing what it's there to do — waste not explained by the mechanism.
There’s avoidable waste on the page
6/10 expected
Page space and pacing emphasize the wrong beats — the important turn is rushed/buried while minor business is lingered on.
The parts are ordered and seamed so they build
7/10 core
The reader can follow what matters
4/10 light
It plays close to the version we’ve seen before
This scene's role doesn't owe this, so a low reading here is neutral rather than a fault.
5/10 light
The beats can be called before they land
This scene's role doesn't owe this, so a low reading here is neutral rather than a fault.
6/10 expected
The feeling comes off the page
7/10 core
The exit pulls you into the next one
This scene has been scored but its written read hasn’t been generated yet — the notes above are derived from the scores.
No explanation provided.
No explanation provided.
“Grab ‘em by the throat and never let ‘em go.”
The scene level score is the impact on the reader or audience to continue reading.
The Script score is how compelled they are to keep reading based on the rest of the script so far.
The scene ends on a strong cliffhanger with the loss of both divers and a new threat on the surface, creating a clear open question about what the creature is and what happens next, compelling the reader to continue.
The script has built momentum through political intrigue, Wakanda's defensive actions, and now a mysterious underwater threat. The vibranium discovery and the attack add a new, dangerous layer to the global conflict, maintaining strong cumulative interest.
All three lenses are solid — worth protecting as it stands.
HoldingA real force keeps it pushing forward.
Craft Read is the familiar battery — concept, plot, characters, dialogue, stakes, pacing.
Scene Mechanics is twelve specific ways a scene stalls — it ends about where it started, nothing is really pushing it, you can call the beats before they land — with about forty finer versions underneath them. So when a scene drags, you find out what's dragging it — not just how much.
7/10 core
It commits to one clear thing and holds it
8/10 core
A real force keeps it pushing forward
6/10 expected
The situation deepens as it goes
7/10 core
It turns — something is different by the end
8/10 expected
What happens here obliges what comes next
6/10 expected
Every beat and line earns its place
7/10 expected
The parts are ordered and seamed so they build
8/10 core
The reader can follow what matters
5/10 light
It plays close to the version we’ve seen before
This scene's role doesn't owe this, so a low reading here is neutral rather than a fault.
6/10 light
It defeats anticipation fairly
This scene's role doesn't owe this, so a low reading here is neutral rather than a fault.
7/10 core
The feeling comes off the page
8/10 core
The exit pulls you into the next one
This scene has been scored but its written read hasn’t been generated yet — the notes above are derived from the scores.
No explanation provided.
No explanation provided.
“Grab ‘em by the throat and never let ‘em go.”
The scene level score is the impact on the reader or audience to continue reading.
The Script score is how compelled they are to keep reading based on the rest of the script so far.
This scene ends on a cliffhanger (helicopter escape, Talocanil still present) and introduces a major new threat, making the reader want to see what happens next to Dr. Graham and how the Talocanil will be confronted.
The script has built momentum through the UN hearing, the Dora Milaje action, and the vibranium discovery. This scene introduces a powerful new antagonist faction, raising the stakes and opening new story threads, compelling the reader to continue.
No lens is broken, but Design, Execution and Read are soft — this reads as a polish pass.
An aftermath beat lands the cost of what just happened rather than driving new action.
HoldingThe reader can follow what matters.
Craft Read is the familiar battery — concept, plot, characters, dialogue, stakes, pacing.
Scene Mechanics is twelve specific ways a scene stalls — it ends about where it started, nothing is really pushing it, you can call the beats before they land — with about forty finer versions underneath them. So when a scene drags, you find out what's dragging it — not just how much.
4/10 core
Several candidate threads compete and none governs — the scene splits its focus rather than committing to one determinate spine.
It isn’t clearly about one thing yet
6/10 core
A real force keeps it pushing forward
4/10 expected
Beats restate the same note; the reader’s experience does not change across the scene.
It restates its note rather than deepening it
5/10 core
It ends about where it started
6/10 expected
What happens here obliges what comes next
5/10 expected
The scene reaches its function and keeps going, or carries beats/lines cuttable without losing what it's there to do — waste not explained by the mechanism.
There’s avoidable waste on the page
6/10 expected
The parts are ordered and seamed so they build
7/10 core
The reader can follow what matters
3/10 light
It plays close to the version we’ve seen before
This scene's role doesn't owe this, so a low reading here is neutral rather than a fault.
4/10 light
The beats can be called before they land
This scene's role doesn't owe this, so a low reading here is neutral rather than a fault.
5/10 expected
The emotion is described on the page rather than produced through the beats.
The feeling is stated more than felt
6/10 core
The exit pulls you into the next one
This scene has been scored but its written read hasn’t been generated yet — the notes above are derived from the scores.
No explanation provided.
No explanation provided.
“Grab ‘em by the throat and never let ‘em go.”
The scene level score is the impact on the reader or audience to continue reading.
The Script score is how compelled they are to keep reading based on the rest of the script so far.
The scene ends with a cliffhanger (helicopter dragged underwater, ship exploding) and the introduction of Namor, creating strong suspense. The reader wants to know what happens to Dr. Graham and what Namor's plan is, compelling them to continue.
The script has built momentum through the UN political drama, the Dora Milaje action, and the CIA investigation. This scene introduces a major new threat (Talocanil) that raises the stakes for Wakanda and the world, making the reader eager to see how Ramonda and Shuri will respond.
All three lenses are solid — worth protecting as it stands.
HoldingThe reader can follow what matters.
Craft Read is the familiar battery — concept, plot, characters, dialogue, stakes, pacing.
Scene Mechanics is twelve specific ways a scene stalls — it ends about where it started, nothing is really pushing it, you can call the beats before they land — with about forty finer versions underneath them. So when a scene drags, you find out what's dragging it — not just how much.
7/10 core
It commits to one clear thing and holds it
6/10 core
A real force keeps it pushing forward
7/10 expected
The situation deepens as it goes
7/10 core
It turns — something is different by the end
6/10 expected
What happens here obliges what comes next
6/10 expected
Every beat and line earns its place
7/10 expected
The parts are ordered and seamed so they build
8/10 core
The reader can follow what matters
5/10 light
It plays close to the version we’ve seen before
This scene's role doesn't owe this, so a low reading here is neutral rather than a fault.
5/10 light
The beats can be called before they land
This scene's role doesn't owe this, so a low reading here is neutral rather than a fault.
7/10 expected
The feeling comes off the page
7/10 core
The exit pulls you into the next one
This scene has been scored but its written read hasn’t been generated yet — the notes above are derived from the scores.
No explanation provided.
No explanation provided.
“Grab ‘em by the throat and never let ‘em go.”
The scene level score is the impact on the reader or audience to continue reading.
The Script score is how compelled they are to keep reading based on the rest of the script so far.
The scene ends with Shuri agreeing to go with Ramonda, creating mild curiosity about where they're going, but it's a soft cliffhanger that doesn't urgently demand the next scene.
Given the script so far, the unresolved threats (Namor, vibranium theft, global tensions) and Shuri's emotional arc create momentum, but this scene is a breather that slows the pace without adding new plot hooks.
All three lenses are solid — worth protecting as it stands.
A ritual beat repeats a known pattern on purpose, so movement and freshness read low by design.
HoldingThe reader can follow what matters.
Craft Read is the familiar battery — concept, plot, characters, dialogue, stakes, pacing.
Scene Mechanics is twelve specific ways a scene stalls — it ends about where it started, nothing is really pushing it, you can call the beats before they land — with about forty finer versions underneath them. So when a scene drags, you find out what's dragging it — not just how much.
8/10 core
It commits to one clear thing and holds it
7/10 core
A real force keeps it pushing forward
7/10 expected
The situation deepens as it goes
8/10 core
It turns — something is different by the end
6/10 expected
What happens here obliges what comes next
7/10 expected
Every beat and line earns its place
7/10 expected
The parts are ordered and seamed so they build
9/10 core
The reader can follow what matters
6/10 expected
It’s a fresh take on this kind of scene
5/10 light
The beats can be called before they land
This scene's role doesn't owe this, so a low reading here is neutral rather than a fault.
8/10 core
The feeling comes off the page
7/10 expected
The exit pulls you into the next one
This scene has been scored but its written read hasn’t been generated yet — the notes above are derived from the scores.
No explanation provided.
No explanation provided.
“Grab ‘em by the throat and never let ‘em go.”
The scene level score is the impact on the reader or audience to continue reading.
The Script score is how compelled they are to keep reading based on the rest of the script so far.
The scene ends on a note of emotional openness—Shuri has confessed her rage, and Ramonda offers compassion. This creates a desire to see what Shuri will do next: will she burn the clothes? Will she begin to heal? The scene compels continuation.
Given the whole script so far, the unresolved external conflicts (Namor, the UN, the search for vibranium) are still active, but this scene deepens the emotional core. The reader is pulled forward by both the external plot and the need to see Shuri's character arc resolve.
All three lenses are solid — worth protecting as it stands.
HoldingThe reader can follow what matters.
Craft Read is the familiar battery — concept, plot, characters, dialogue, stakes, pacing.
Scene Mechanics is twelve specific ways a scene stalls — it ends about where it started, nothing is really pushing it, you can call the beats before they land — with about forty finer versions underneath them. So when a scene drags, you find out what's dragging it — not just how much.
8/10 core
It commits to one clear thing and holds it
8/10 core
A real force keeps it pushing forward
7/10 core
The situation deepens as it goes
8/10 core
It turns — something is different by the end
8/10 core
What happens here obliges what comes next
7/10 expected
Every beat and line earns its place
8/10 expected
The parts are ordered and seamed so they build
9/10 expected
The reader can follow what matters
6/10 light
It’s a fresh take on this kind of scene
This scene's role doesn't owe this, so a low reading here is neutral rather than a fault.
7/10 light
It defeats anticipation fairly
This scene's role doesn't owe this, so a low reading here is neutral rather than a fault.
7/10 light
The feeling comes off the page
This scene's role doesn't owe this, so a low reading here is neutral rather than a fault.
8/10 light
The exit pulls you into the next one
This scene's role doesn't owe this, so a low reading here is neutral rather than a fault.
This scene has been scored but its written read hasn’t been generated yet — the notes above are derived from the scores.
No explanation provided.
No explanation provided.
“Grab ‘em by the throat and never let ‘em go.”
The scene level score is the impact on the reader or audience to continue reading.
The Script score is how compelled they are to keep reading based on the rest of the script so far.
This scene compels the reader to continue because it ends with a major cliffhanger (the vibranium detector by the fire) and raises urgent questions: Will Wakanda help Namor? Who is the scientist? What will happen next?
Given the whole script so far, the reader is strongly compelled to continue because the story has built multiple threads: Shuri's grief, Wakanda's political struggles, the underwater vibranium threat, and Namor's mysterious civilization. The momentum is high, and the scene adds a new, powerful antagonist.
No lens is broken, but Design and Read are soft — this reads as a polish pass.
HoldingThe reader can follow what matters.
Craft Read is the familiar battery — concept, plot, characters, dialogue, stakes, pacing.
Scene Mechanics is twelve specific ways a scene stalls — it ends about where it started, nothing is really pushing it, you can call the beats before they land — with about forty finer versions underneath them. So when a scene drags, you find out what's dragging it — not just how much.
6/10 core
It commits to one clear thing and holds it
6/10 core
A real force keeps it pushing forward
5/10 expected
Beats restate the same note; the reader’s experience does not change across the scene.
It restates its note rather than deepening it
5/10 core
The unit connects, displays, or frames — it never attempts to change a dramatic condition. Distinct from a turn that is attempted but does not land (unclear_turn). An interlude doing its intended job is a craft choice, not this flaw.
It ends about where it started
6/10 expected
What happens here obliges what comes next
6/10 expected
Every beat and line earns its place
6/10 expected
The parts are ordered and seamed so they build
7/10 core
The reader can follow what matters
4/10 light
It plays close to the version we’ve seen before
This scene's role doesn't owe this, so a low reading here is neutral rather than a fault.
4/10 light
The beats can be called before they land
This scene's role doesn't owe this, so a low reading here is neutral rather than a fault.
5/10 expected
The emotion is described on the page rather than produced through the beats.
The feeling is stated more than felt
6/10 core
The exit pulls you into the next one
This scene has been scored but its written read hasn’t been generated yet — the notes above are derived from the scores.
No explanation provided.
No explanation provided.
“Grab ‘em by the throat and never let ‘em go.”
The scene level score is the impact on the reader or audience to continue reading.
The Script score is how compelled they are to keep reading based on the rest of the script so far.
The scene ends with Ramonda considering M'Baku's point, leaving the council's decision unresolved. This creates a moderate hook—readers want to know what they decide—but the scene feels self-contained as a debate.
The script so far has built strong momentum with Namor's introduction, the UN confrontation, and the underwater attack. This council scene maintains that momentum by deepening the political stakes, though it slows the pace slightly. The unresolved threat and Ramonda's leadership arc keep the reader invested.
No lens is broken, but Design and Read are soft — this reads as a polish pass.
HoldingThe reader can follow what matters.
Craft Read is the familiar battery — concept, plot, characters, dialogue, stakes, pacing.
Scene Mechanics is twelve specific ways a scene stalls — it ends about where it started, nothing is really pushing it, you can call the beats before they land — with about forty finer versions underneath them. So when a scene drags, you find out what's dragging it — not just how much.
7/10 core
It commits to one clear thing and holds it
6/10 core
A real force keeps it pushing forward
5/10 expected
Beats restate the same note; the reader’s experience does not change across the scene.
It restates its note rather than deepening it
5/10 core
The unit connects, displays, or frames — it never attempts to change a dramatic condition. Distinct from a turn that is attempted but does not land (unclear_turn). An interlude doing its intended job is a craft choice, not this flaw.
It ends about where it started
7/10 expected
What happens here obliges what comes next
6/10 expected
Every beat and line earns its place
6/10 expected
The parts are ordered and seamed so they build
8/10 core
The reader can follow what matters
4/10 light
It plays close to the version we’ve seen before
This scene's role doesn't owe this, so a low reading here is neutral rather than a fault.
4/10 light
The beats can be called before they land
This scene's role doesn't owe this, so a low reading here is neutral rather than a fault.
5/10 expected
The emotion is described on the page rather than produced through the beats.
The feeling is stated more than felt
7/10 core
The exit pulls you into the next one
This scene has been scored but its written read hasn’t been generated yet — the notes above are derived from the scores.
No explanation provided.
No explanation provided.
“Grab ‘em by the throat and never let ‘em go.”
The scene level score is the impact on the reader or audience to continue reading.
The Script score is how compelled they are to keep reading based on the rest of the script so far.
This scene compels the reader to continue because it sets up a clear mission (find the scientist) and introduces a new character (the unknown inventor), creating curiosity about who they are and how they'll be found.
Given the whole script so far, the reader is pulled forward by the unresolved threat of Namor, the mystery of the scientist, and Shuri's emotional arc. This scene adds a new thread (the mission) but doesn't escalate existing tensions, so momentum holds steady.
All three lenses are solid — worth protecting as it stands.
HoldingThe reader can follow what matters.
Craft Read is the familiar battery — concept, plot, characters, dialogue, stakes, pacing.
Scene Mechanics is twelve specific ways a scene stalls — it ends about where it started, nothing is really pushing it, you can call the beats before they land — with about forty finer versions underneath them. So when a scene drags, you find out what's dragging it — not just how much.
7/10 core
It commits to one clear thing and holds it
6/10 core
A real force keeps it pushing forward
6/10 expected
The situation deepens as it goes
7/10 core
It turns — something is different by the end
7/10 expected
What happens here obliges what comes next
6/10 expected
Every beat and line earns its place
7/10 expected
The parts are ordered and seamed so they build
8/10 core
The reader can follow what matters
5/10 light
It plays close to the version we’ve seen before
This scene's role doesn't owe this, so a low reading here is neutral rather than a fault.
5/10 light
The beats can be called before they land
This scene's role doesn't owe this, so a low reading here is neutral rather than a fault.
6/10 expected
The feeling comes off the page
7/10 core
The exit pulls you into the next one
This scene has been scored but its written read hasn’t been generated yet — the notes above are derived from the scores.
No explanation provided.
No explanation provided.
“Grab ‘em by the throat and never let ‘em go.”
The scene level score is the impact on the reader or audience to continue reading.
The Script score is how compelled they are to keep reading based on the rest of the script so far.
The scene ends with Riri's shocked 'WHAT?!' after hearing about Namor, creating a strong cliffhanger that compels the reader to see her reaction and whether she agrees to go to Wakanda.
The script has strong cumulative momentum: the Namor threat is escalating, Shuri's grief arc is simmering, and now a new character with high stakes is introduced. The playful tone here provides a necessary breather, but the overall tension remains high.
All three lenses are solid — worth protecting as it stands.
HoldingA real force keeps it pushing forward.
Craft Read is the familiar battery — concept, plot, characters, dialogue, stakes, pacing.
Scene Mechanics is twelve specific ways a scene stalls — it ends about where it started, nothing is really pushing it, you can call the beats before they land — with about forty finer versions underneath them. So when a scene drags, you find out what's dragging it — not just how much.
7/10 core
It commits to one clear thing and holds it
8/10 core
A real force keeps it pushing forward
6/10 expected
The situation deepens as it goes
7/10 core
It turns — something is different by the end
8/10 expected
What happens here obliges what comes next
6/10 expected
Every beat and line earns its place
7/10 expected
The parts are ordered and seamed so they build
8/10 core
The reader can follow what matters
5/10 light
It plays close to the version we’ve seen before
This scene's role doesn't owe this, so a low reading here is neutral rather than a fault.
6/10 light
It defeats anticipation fairly
This scene's role doesn't owe this, so a low reading here is neutral rather than a fault.
7/10 core
The feeling comes off the page
8/10 core
The exit pulls you into the next one
This scene has been scored but its written read hasn’t been generated yet — the notes above are derived from the scores.
No explanation provided.
No explanation provided.
“Grab ‘em by the throat and never let ‘em go.”
The scene level score is the impact on the reader or audience to continue reading.
The Script score is how compelled they are to keep reading based on the rest of the script so far.
The scene ends on a cliffhanger with Shuri dropping the Kimoyo bead, leaving the reader wondering how they'll escape. The immediate threat of the Feds and the unresolved question of Ross's betrayal compel the reader to continue.
The script has multiple open threads: the mission to find the scientist, Namor's threat, and the political fallout from the UN. This scene adds a new layer of urgency, and the characters' dynamics are engaging, keeping the reader invested in the overall story.
All three lenses are solid — worth protecting as it stands.
HoldingThe reader can follow what matters.
Craft Read is the familiar battery — concept, plot, characters, dialogue, stakes, pacing.
Scene Mechanics is twelve specific ways a scene stalls — it ends about where it started, nothing is really pushing it, you can call the beats before they land — with about forty finer versions underneath them. So when a scene drags, you find out what's dragging it — not just how much.
7/10 core
It commits to one clear thing and holds it
7/10 core
A real force keeps it pushing forward
6/10 expected
The situation deepens as it goes
7/10 core
It turns — something is different by the end
7/10 expected
What happens here obliges what comes next
6/10 expected
Every beat and line earns its place
7/10 expected
The parts are ordered and seamed so they build
8/10 core
The reader can follow what matters
5/10 light
It plays close to the version we’ve seen before
This scene's role doesn't owe this, so a low reading here is neutral rather than a fault.
6/10 light
It defeats anticipation fairly
This scene's role doesn't owe this, so a low reading here is neutral rather than a fault.
7/10 expected
The feeling comes off the page
8/10 core
The exit pulls you into the next one
This scene has been scored but its written read hasn’t been generated yet — the notes above are derived from the scores.
No explanation provided.
No explanation provided.
“Grab ‘em by the throat and never let ‘em go.”
The scene level score is the impact on the reader or audience to continue reading.
The Script score is how compelled they are to keep reading based on the rest of the script so far.
This scene compels continuation because it ends mid-escape with the Barracuda crashing out, leaving the chase unresolved and Riri airborne—creating immediate suspense.
Given the whole script, the momentum is strong: Namor's threat, the FBI pursuit, and Riri's introduction all converge. The escape raises stakes and promises more action, keeping the reader invested.
All three lenses are solid — worth protecting as it stands.
HoldingIt commits to one clear thing and holds it.
Craft Read is the familiar battery — concept, plot, characters, dialogue, stakes, pacing.
Scene Mechanics is twelve specific ways a scene stalls — it ends about where it started, nothing is really pushing it, you can call the beats before they land — with about forty finer versions underneath them. So when a scene drags, you find out what's dragging it — not just how much.
7/10 core
It commits to one clear thing and holds it
7/10 core
A real force keeps it pushing forward
5/10 expected
The surface is full of events and motion, but the governing thread ends where it started — activity substitutes for evolution. Distinct from beats literally restating the same note.
It restates its note rather than deepening it
6/10 core
It turns — something is different by the end
6/10 expected
What happens here obliges what comes next
5/10 expected
The scene reaches its function and keeps going, or carries beats/lines cuttable without losing what it's there to do — waste not explained by the mechanism.
There’s avoidable waste on the page
6/10 expected
The parts are ordered and seamed so they build
7/10 core
The reader can follow what matters
4/10 light
The scene's main situation/image/beat-pattern is recognizable genre convention and the script adds no specific inversion, collision, POV, cost, world-rule, or tonal twist that changes how it plays.
It plays close to the version we’ve seen before
This scene's role doesn't owe this, so a low reading here is neutral rather than a fault.
4/10 light
The scene sets up its conflict then plays the most likely version — no turn, reversal, complication, or reveal the reader couldn't call in advance.
The beats can be called before they land
This scene's role doesn't owe this, so a low reading here is neutral rather than a fault.
6/10 expected
The feeling comes off the page
7/10 core
The exit pulls you into the next one
This scene has been scored but its written read hasn’t been generated yet — the notes above are derived from the scores.
No explanation provided.
No explanation provided.
“Grab ‘em by the throat and never let ‘em go.”
The scene level score is the impact on the reader or audience to continue reading.
The Script score is how compelled they are to keep reading based on the rest of the script so far.
The scene ends with Okoye asking 'Shuri, where are you?' which creates a mild cliffhanger about their reunion. The action is unresolved, making the reader want to see how they regroup.
Given the whole script, the chase is a high-energy interlude but doesn't advance the main Namor plot. The unresolved threat of Namor and the need to protect Riri keep the reader invested, but the action here feels like a detour.
No lens is broken, but Design, Execution and Read are soft — this reads as a polish pass.
HoldingA real force keeps it pushing forward.
Craft Read is the familiar battery — concept, plot, characters, dialogue, stakes, pacing.
Scene Mechanics is twelve specific ways a scene stalls — it ends about where it started, nothing is really pushing it, you can call the beats before they land — with about forty finer versions underneath them. So when a scene drags, you find out what's dragging it — not just how much.
4/10 core
Several candidate threads compete and none governs — the scene splits its focus rather than committing to one determinate spine.
It isn’t clearly about one thing yet
7/10 core
A real force keeps it pushing forward
4/10 expected
The surface is full of events and motion, but the governing thread ends where it started — activity substitutes for evolution. Distinct from beats literally restating the same note.
It restates its note rather than deepening it
5/10 core
The unit connects, displays, or frames — it never attempts to change a dramatic condition. Distinct from a turn that is attempted but does not land (unclear_turn). An interlude doing its intended job is a craft choice, not this flaw.
It ends about where it started
6/10 expected
What happens here obliges what comes next
5/10 expected
The scene reaches its function and keeps going, or carries beats/lines cuttable without losing what it's there to do — waste not explained by the mechanism.
There’s avoidable waste on the page
5/10 expected
The scene/sequence shifts location, time, POV, mode, or thread without making the causal/spatial/emotional/rhythmic relationship between adjacent chunks legible.
The parts sit side by side rather than building
6/10 core
The reader can follow what matters
4/10 expected
The scene's main situation/image/beat-pattern is recognizable genre convention and the script adds no specific inversion, collision, POV, cost, world-rule, or tonal twist that changes how it plays.
It plays close to the version we’ve seen before
4/10 expected
The scene sets up its conflict then plays the most likely version — no turn, reversal, complication, or reveal the reader couldn't call in advance.
The beats can be called before they land
5/10 expected
The feeling is stated more than felt
6/10 core
The exit pulls you into the next one
This scene has been scored but its written read hasn’t been generated yet — the notes above are derived from the scores.
No explanation provided.
No explanation provided.
“Grab ‘em by the throat and never let ‘em go.”
The scene level score is the impact on the reader or audience to continue reading.
The Script score is how compelled they are to keep reading based on the rest of the script so far.
This scene ends on a cliffhanger with the drone and Riri's altitude issue unresolved, and Shuri still being chased. The reader will want to see if Riri can reach the drone and if the escape succeeds.
The script has strong momentum from the UN hearing, the Mali raid, the Namor introduction, and now the FBI chase. The unresolved threats (Namor, the drone, the FBI) and the character dynamics (Shuri's grief, Okoye's duty) keep the reader invested.
No lens is broken, but Design, Execution and Read are soft — this reads as a polish pass.
HoldingA real force keeps it pushing forward.
Craft Read is the familiar battery — concept, plot, characters, dialogue, stakes, pacing.
Scene Mechanics is twelve specific ways a scene stalls — it ends about where it started, nothing is really pushing it, you can call the beats before they land — with about forty finer versions underneath them. So when a scene drags, you find out what's dragging it — not just how much.
4/10 core
Several candidate threads compete and none governs — the scene splits its focus rather than committing to one determinate spine.
It isn’t clearly about one thing yet
6/10 core
A real force keeps it pushing forward
4/10 expected
The surface is full of events and motion, but the governing thread ends where it started — activity substitutes for evolution. Distinct from beats literally restating the same note.
It restates its note rather than deepening it
5/10 core
It ends about where it started
6/10 expected
What happens here obliges what comes next
5/10 expected
The scene reaches its function and keeps going, or carries beats/lines cuttable without losing what it's there to do — waste not explained by the mechanism.
There’s avoidable waste on the page
5/10 expected
The scene/sequence shifts location, time, POV, mode, or thread without making the causal/spatial/emotional/rhythmic relationship between adjacent chunks legible.
The parts sit side by side rather than building
6/10 core
The reader can follow what matters
3/10 light
It plays close to the version we’ve seen before
This scene's role doesn't owe this, so a low reading here is neutral rather than a fault.
4/10 light
The beats can be called before they land
This scene's role doesn't owe this, so a low reading here is neutral rather than a fault.
5/10 expected
The feeling is stated more than felt
6/10 core
The exit pulls you into the next one
This scene has been scored but its written read hasn’t been generated yet — the notes above are derived from the scores.
No explanation provided.
No explanation provided.
“Grab ‘em by the throat and never let ‘em go.”
The scene level score is the impact on the reader or audience to continue reading.
The Script score is how compelled they are to keep reading based on the rest of the script so far.
This scene compels the reader to continue because the escape is not yet complete—the blockade is cleared but the characters are still in danger, and the next scene likely shows their extraction or further pursuit.
Given the whole script so far, the reader is pulled to continue because the Namor threat remains unresolved, Riri's role is still developing, and the chase sequence has built strong momentum. The action is satisfying but the larger plot questions (what does Namor want? how will Wakanda respond?) keep the reader invested.
All three lenses are solid — worth protecting as it stands.
HoldingA real force keeps it pushing forward.
Craft Read is the familiar battery — concept, plot, characters, dialogue, stakes, pacing.
Scene Mechanics is twelve specific ways a scene stalls — it ends about where it started, nothing is really pushing it, you can call the beats before they land — with about forty finer versions underneath them. So when a scene drags, you find out what's dragging it — not just how much.
7/10 core
It commits to one clear thing and holds it
8/10 core
A real force keeps it pushing forward
6/10 expected
The situation deepens as it goes
7/10 core
It turns — something is different by the end
8/10 core
What happens here obliges what comes next
6/10 expected
Every beat and line earns its place
7/10 expected
The parts are ordered and seamed so they build
8/10 core
The reader can follow what matters
5/10 light
It plays close to the version we’ve seen before
This scene's role doesn't owe this, so a low reading here is neutral rather than a fault.
6/10 light
It defeats anticipation fairly
This scene's role doesn't owe this, so a low reading here is neutral rather than a fault.
7/10 expected
The feeling comes off the page
8/10 core
The exit pulls you into the next one
This scene has been scored but its written read hasn’t been generated yet — the notes above are derived from the scores.
No explanation provided.
No explanation provided.
“Grab ‘em by the throat and never let ‘em go.”
The scene level score is the impact on the reader or audience to continue reading.
The Script score is how compelled they are to keep reading based on the rest of the script so far.
The scene ends with Shuri and Riri captured, Okoye swept away, and a clear cliffhanger—what will Namor do? This strongly compels the reader to continue to the next scene.
Given the whole script so far, the capture of Shuri and Riri raises the stakes and promises a confrontation with Namor, while Okoye's fate is uncertain. The momentum is strong, with multiple threads (vibranium detector, Talocanil threat, Shuri's grief) converging.
No lens is broken, but Design and Read are soft — this reads as a polish pass.
HoldingWhat happens here obliges what comes next.
Craft Read is the familiar battery — concept, plot, characters, dialogue, stakes, pacing.
Scene Mechanics is twelve specific ways a scene stalls — it ends about where it started, nothing is really pushing it, you can call the beats before they land — with about forty finer versions underneath them. So when a scene drags, you find out what's dragging it — not just how much.
6/10 core
It commits to one clear thing and holds it
4/10 core
The scene asserts tension/stakes/unease but no locatable page-visible force produces it — mood is mistaken for pressure (the pressure firewall).
It leans on mood instead of something actually pushing it
4/10 expected
Beats restate the same note; the reader’s experience does not change across the scene.
It restates its note rather than deepening it
5/10 core
The unit connects, displays, or frames — it never attempts to change a dramatic condition. Distinct from a turn that is attempted but does not land (unclear_turn). An interlude doing its intended job is a craft choice, not this flaw.
It ends about where it started
7/10 expected
What happens here obliges what comes next
6/10 expected
Every beat and line earns its place
6/10 expected
The parts are ordered and seamed so they build
7/10 core
The reader can follow what matters
4/10 light
It plays close to the version we’ve seen before
This scene's role doesn't owe this, so a low reading here is neutral rather than a fault.
5/10 light
The beats can be called before they land
This scene's role doesn't owe this, so a low reading here is neutral rather than a fault.
4/10 expected
The emotion is described on the page rather than produced through the beats.
The feeling is stated more than felt
7/10 core
The exit pulls you into the next one
This scene has been scored but its written read hasn’t been generated yet — the notes above are derived from the scores.
No explanation provided.
No explanation provided.
“Grab ‘em by the throat and never let ‘em go.”
The scene level score is the impact on the reader or audience to continue reading.
The Script score is how compelled they are to keep reading based on the rest of the script so far.
The scene compels continuation by ending with a clear hook: Ross has the bracelet, Val is taking him on a road trip, and the audience wants to see what he does with it and how the investigation unfolds.
Given the whole script, the momentum is strong: the capture of Shuri and Riri, the introduction of Namor, and now Ross's secret possession of the bracelet create multiple threads that pull the reader forward. The scene maintains but doesn't dramatically increase this momentum.
All three lenses are solid — worth protecting as it stands.
An aftermath beat lands the cost of what just happened rather than driving new action.
HoldingWhat happens here obliges what comes next.
Craft Read is the familiar battery — concept, plot, characters, dialogue, stakes, pacing.
Scene Mechanics is twelve specific ways a scene stalls — it ends about where it started, nothing is really pushing it, you can call the beats before they land — with about forty finer versions underneath them. So when a scene drags, you find out what's dragging it — not just how much.
7/10 core
It commits to one clear thing and holds it
7/10 core
A real force keeps it pushing forward
6/10 expected
The situation deepens as it goes
7/10 core
It turns — something is different by the end
8/10 core
What happens here obliges what comes next
6/10 expected
Every beat and line earns its place
7/10 expected
The parts are ordered and seamed so they build
8/10 core
The reader can follow what matters
5/10 light
It plays close to the version we’ve seen before
This scene's role doesn't owe this, so a low reading here is neutral rather than a fault.
5/10 light
The beats can be called before they land
This scene's role doesn't owe this, so a low reading here is neutral rather than a fault.
8/10 core
The feeling comes off the page
8/10 core
The exit pulls you into the next one
This scene has been scored but its written read hasn’t been generated yet — the notes above are derived from the scores.
No explanation provided.
No explanation provided.
“Grab ‘em by the throat and never let ‘em go.”
The scene level score is the impact on the reader or audience to continue reading.
The Script score is how compelled they are to keep reading based on the rest of the script so far.
The scene ends with a clear emotional cliffhanger—Okoye's dismissal and Ayo's promotion—and the unresolved fate of Shuri, compelling the reader to see how Okoye will respond and what happens next.
The script has strong momentum from the abduction and the political fallout, with multiple threads (Shuri's capture, Okoye's disgrace, Namor's threat) converging, keeping the reader invested in the cumulative story.
No lens is broken, but Design and Read are soft — this reads as a polish pass.
A transition carries us between beats. It owes less structurally than a scene built to turn.
HoldingThe reader can follow what matters.
Craft Read is the familiar battery — concept, plot, characters, dialogue, stakes, pacing.
Scene Mechanics is twelve specific ways a scene stalls — it ends about where it started, nothing is really pushing it, you can call the beats before they land — with about forty finer versions underneath them. So when a scene drags, you find out what's dragging it — not just how much.
6/10 core
It commits to one clear thing and holds it
4/10 core
The scene asserts tension/stakes/unease but no locatable page-visible force produces it — mood is mistaken for pressure (the pressure firewall).
It leans on mood instead of something actually pushing it
4/10 expected
Beats restate the same note; the reader’s experience does not change across the scene.
It restates its note rather than deepening it
5/10 core
The unit connects, displays, or frames — it never attempts to change a dramatic condition. Distinct from a turn that is attempted but does not land (unclear_turn). An interlude doing its intended job is a craft choice, not this flaw.
It ends about where it started
6/10 expected
What happens here obliges what comes next
6/10 core
Every beat and line earns its place
6/10 expected
The parts are ordered and seamed so they build
7/10 core
The reader can follow what matters
4/10 light
It plays close to the version we’ve seen before
This scene's role doesn't owe this, so a low reading here is neutral rather than a fault.
4/10 light
The beats can be called before they land
This scene's role doesn't owe this, so a low reading here is neutral rather than a fault.
4/10 light
The feeling is stated more than felt
This scene's role doesn't owe this, so a low reading here is neutral rather than a fault.
6/10 core
The exit pulls you into the next one
This scene has been scored but its written read hasn’t been generated yet — the notes above are derived from the scores.
No explanation provided.
No explanation provided.
“Grab ‘em by the throat and never let ‘em go.”
The scene level score is the impact on the reader or audience to continue reading.
The Script score is how compelled they are to keep reading based on the rest of the script so far.
The scene ends with Ross calling Ramonda, which creates a clear hook: what will they discuss? How will Ross help? The reader wants to see the next scene to learn the plan.
The script has strong momentum from the bridge attack and the capture of Shuri and Riri. This scene maintains that momentum by introducing a new ally (Ross) and a new threat (Val). The threads of the rescue and the CIA pursuit are both active, pulling the reader forward.
No lens is broken, but Design and Read are soft — this reads as a polish pass.
HoldingWhat happens here obliges what comes next.
Craft Read is the familiar battery — concept, plot, characters, dialogue, stakes, pacing.
Scene Mechanics is twelve specific ways a scene stalls — it ends about where it started, nothing is really pushing it, you can call the beats before they land — with about forty finer versions underneath them. So when a scene drags, you find out what's dragging it — not just how much.
6/10 core
It commits to one clear thing and holds it
4/10 core
The scene asserts tension/stakes/unease but no locatable page-visible force produces it — mood is mistaken for pressure (the pressure firewall).
It leans on mood instead of something actually pushing it
4/10 expected
Beats restate the same note; the reader’s experience does not change across the scene.
It restates its note rather than deepening it
5/10 core
The unit connects, displays, or frames — it never attempts to change a dramatic condition. Distinct from a turn that is attempted but does not land (unclear_turn). An interlude doing its intended job is a craft choice, not this flaw.
It ends about where it started
7/10 expected
What happens here obliges what comes next
6/10 expected
Every beat and line earns its place
6/10 expected
The parts are ordered and seamed so they build
7/10 core
The reader can follow what matters
4/10 light
It plays close to the version we’ve seen before
This scene's role doesn't owe this, so a low reading here is neutral rather than a fault.
4/10 light
The beats can be called before they land
This scene's role doesn't owe this, so a low reading here is neutral rather than a fault.
5/10 expected
The emotion is described on the page rather than produced through the beats.
The feeling is stated more than felt
6/10 core
The exit pulls you into the next one
This scene has been scored but its written read hasn’t been generated yet — the notes above are derived from the scores.
No explanation provided.
No explanation provided.
“Grab ‘em by the throat and never let ‘em go.”
The scene level score is the impact on the reader or audience to continue reading.
The Script score is how compelled they are to keep reading based on the rest of the script so far.
The scene compels continuation through the conch ritual cliffhanger—readers want to see what happens when Ramonda blows the shell. The open question of whether Namor will respond drives momentum.
The script maintains strong momentum through the abduction of Shuri and Riri, the political fallout, and now the conch ritual. The threads of Ross's loyalty, the laptop encryption, and Namor's threat are all active, keeping the reader invested.
All three lenses are solid — worth protecting as it stands.
HoldingWhat happens here obliges what comes next.
Craft Read is the familiar battery — concept, plot, characters, dialogue, stakes, pacing.
Scene Mechanics is twelve specific ways a scene stalls — it ends about where it started, nothing is really pushing it, you can call the beats before they land — with about forty finer versions underneath them. So when a scene drags, you find out what's dragging it — not just how much.
7/10 core
It commits to one clear thing and holds it
7/10 core
A real force keeps it pushing forward
6/10 expected
The situation deepens as it goes
7/10 core
It turns — something is different by the end
8/10 core
What happens here obliges what comes next
6/10 expected
Every beat and line earns its place
6/10 expected
The parts are ordered and seamed so they build
8/10 core
The reader can follow what matters
5/10 light
It plays close to the version we’ve seen before
This scene's role doesn't owe this, so a low reading here is neutral rather than a fault.
6/10 light
It defeats anticipation fairly
This scene's role doesn't owe this, so a low reading here is neutral rather than a fault.
7/10 core
The feeling comes off the page
8/10 core
The exit pulls you into the next one
This scene has been scored but its written read hasn’t been generated yet — the notes above are derived from the scores.
No explanation provided.
No explanation provided.
“Grab ‘em by the throat and never let ‘em go.”
The scene level score is the impact on the reader or audience to continue reading.
The Script score is how compelled they are to keep reading based on the rest of the script so far.
The scene ends with a clear hook: Ramonda is going to find Nakia, setting up a rescue mission. The open question of whether she can succeed and the two-day deadline compel the reader to continue.
The script has built strong momentum through the abduction of Shuri and Riri, the stripping of Okoye's rank, and now Ramonda's desperate gambit. The threads of the CIA investigation, the laptop encryption, and Nakia's return all pull the reader forward.
All three lenses are solid — worth protecting as it stands.
HoldingThe reader can follow what matters.
Craft Read is the familiar battery — concept, plot, characters, dialogue, stakes, pacing.
Scene Mechanics is twelve specific ways a scene stalls — it ends about where it started, nothing is really pushing it, you can call the beats before they land — with about forty finer versions underneath them. So when a scene drags, you find out what's dragging it — not just how much.
7/10 core
It commits to one clear thing and holds it
7/10 core
A real force keeps it pushing forward
6/10 expected
The situation deepens as it goes
6/10 core
It turns — something is different by the end
7/10 expected
What happens here obliges what comes next
6/10 expected
Every beat and line earns its place
7/10 expected
The parts are ordered and seamed so they build
8/10 core
The reader can follow what matters
5/10 light
It plays close to the version we’ve seen before
This scene's role doesn't owe this, so a low reading here is neutral rather than a fault.
5/10 light
The beats can be called before they land
This scene's role doesn't owe this, so a low reading here is neutral rather than a fault.
7/10 expected
The feeling comes off the page
8/10 core
The exit pulls you into the next one
This scene has been scored but its written read hasn’t been generated yet — the notes above are derived from the scores.
No explanation provided.
No explanation provided.
“Grab ‘em by the throat and never let ‘em go.”
The scene level score is the impact on the reader or audience to continue reading.
The Script score is how compelled they are to keep reading based on the rest of the script so far.
The scene ends with Nakia's commitment and the reveal of Talocan, creating a clear hook for the next scene (the Mayan Elder encounter). The reader wants to see how Nakia's search unfolds.
The script has strong momentum from Shuri's abduction and Okoye's fall, and this scene provides a necessary emotional reset. The threads of Ramonda's grief, Nakia's return, and the Talocan threat are all gaining steam, keeping the reader invested.
No lens is broken, but Design and Read are soft — this reads as a polish pass.
An orientation beat sets up the world. It isn’t expected to carry a big turn, so a lower Design read here is often the shape of the scene, not a fault.
HoldingThe reader can follow what matters.
Craft Read is the familiar battery — concept, plot, characters, dialogue, stakes, pacing.
Scene Mechanics is twelve specific ways a scene stalls — it ends about where it started, nothing is really pushing it, you can call the beats before they land — with about forty finer versions underneath them. So when a scene drags, you find out what's dragging it — not just how much.
6/10 core
It commits to one clear thing and holds it
4/10 expected
The scene asserts tension/stakes/unease but no locatable page-visible force produces it — mood is mistaken for pressure (the pressure firewall).
It leans on mood instead of something actually pushing it
4/10 light
It restates its note rather than deepening it
This scene's role doesn't owe this, so a low reading here is neutral rather than a fault.
4/10 light
It ends about where it started
This scene's role doesn't owe this, so a low reading here is neutral rather than a fault.
5/10 expected
The scene delivers information or understanding but no one is forced to decide or act on it.
The result doesn’t oblige what comes next
6/10 expected
Every beat and line earns its place
6/10 expected
The parts are ordered and seamed so they build
7/10 core
The reader can follow what matters
4/10 light
The scene's main situation/image/beat-pattern is recognizable genre convention and the script adds no specific inversion, collision, POV, cost, world-rule, or tonal twist that changes how it plays.
It plays close to the version we’ve seen before
This scene's role doesn't owe this, so a low reading here is neutral rather than a fault.
3/10 light
The scene sets up its conflict then plays the most likely version — no turn, reversal, complication, or reveal the reader couldn't call in advance.
The beats can be called before they land
This scene's role doesn't owe this, so a low reading here is neutral rather than a fault.
5/10 expected
The emotion is described on the page rather than produced through the beats.
The feeling is stated more than felt
5/10 expected
At the close there is no open question or live threat — no reason to turn the page.
It settles at the exit rather than pulling on
This scene has been scored but its written read hasn’t been generated yet — the notes above are derived from the scores.
No explanation provided.
No explanation provided.
“Grab ‘em by the throat and never let ‘em go.”
The scene level score is the impact on the reader or audience to continue reading.
The Script score is how compelled they are to keep reading based on the rest of the script so far.
The scene ends with a clear hook: Shuri is led to meet Namor, leaving Riri alone. The reader wants to see what Namor wants and how Shuri will handle the cultural confrontation.
The script has strong cumulative momentum: Shuri's capture, Ramonda's deal with Namor, Nakia's mission, and now the captive scene. The threads are converging, and the reader is invested in Shuri's fate and the looming war.
Design and Read are broken — this reads as a rebuild before polish.
HoldingThe reader can follow what matters.
Craft Read is the familiar battery — concept, plot, characters, dialogue, stakes, pacing.
Scene Mechanics is twelve specific ways a scene stalls — it ends about where it started, nothing is really pushing it, you can call the beats before they land — with about forty finer versions underneath them. So when a scene drags, you find out what's dragging it — not just how much.
4/10 core
Several candidate threads compete and none governs — the scene splits its focus rather than committing to one determinate spine.
It isn’t clearly about one thing yet
4/10 core
The scene asserts tension/stakes/unease but no locatable page-visible force produces it — mood is mistaken for pressure (the pressure firewall).
It leans on mood instead of something actually pushing it
4/10 expected
Beats restate the same note; the reader’s experience does not change across the scene.
It restates its note rather than deepening it
3/10 core
The unit connects, displays, or frames — it never attempts to change a dramatic condition. Distinct from a turn that is attempted but does not land (unclear_turn). An interlude doing its intended job is a craft choice, not this flaw.
It ends about where it started
5/10 expected
The scene delivers information or understanding but no one is forced to decide or act on it.
The result doesn’t oblige what comes next
5/10 expected
The scene reaches its function and keeps going, or carries beats/lines cuttable without losing what it's there to do — waste not explained by the mechanism.
There’s avoidable waste on the page
4/10 expected
Page space and pacing emphasize the wrong beats — the important turn is rushed/buried while minor business is lingered on.
The parts sit side by side rather than building
7/10 core
The reader can follow what matters
4/10 expected
The scene's main situation/image/beat-pattern is recognizable genre convention and the script adds no specific inversion, collision, POV, cost, world-rule, or tonal twist that changes how it plays.
It plays close to the version we’ve seen before
3/10 expected
The scene sets up its conflict then plays the most likely version — no turn, reversal, complication, or reveal the reader couldn't call in advance.
The beats can be called before they land
5/10 core
The emotion is described on the page rather than produced through the beats.
The feeling is stated more than felt
4/10 core
The unit completes its business and ends on a settled beat — no new live question, demand, or expectation is created for the next unit to inherit.
It settles at the exit rather than pulling on
This scene has been scored but its written read hasn’t been generated yet — the notes above are derived from the scores.
No explanation provided.
No explanation provided.
“Grab ‘em by the throat and never let ‘em go.”
The scene level score is the impact on the reader or audience to continue reading.
The Script score is how compelled they are to keep reading based on the rest of the script so far.
The scene ends on a flashback cliffhanger, making the reader want to see the full origin story, but the present-tense plot is paused, reducing urgency.
Given the whole script, the abduction of Shuri and Riri, the political fallout, and Nakia's mission create strong cumulative momentum. This scene provides necessary context but slows the pace.
Read is broken — a load-bearing lens isn’t doing its job yet.
A montage compresses time. It isn’t built to turn on a single thread.
HoldingThe reader can follow what matters.
Craft Read is the familiar battery — concept, plot, characters, dialogue, stakes, pacing.
Scene Mechanics is twelve specific ways a scene stalls — it ends about where it started, nothing is really pushing it, you can call the beats before they land — with about forty finer versions underneath them. So when a scene drags, you find out what's dragging it — not just how much.
6/10 core
It commits to one clear thing and holds it
4/10 expected
The scene asserts tension/stakes/unease but no locatable page-visible force produces it — mood is mistaken for pressure (the pressure firewall).
It leans on mood instead of something actually pushing it
5/10 expected
Beats restate the same note; the reader’s experience does not change across the scene.
It restates its note rather than deepening it
4/10 core
The unit connects, displays, or frames — it never attempts to change a dramatic condition. Distinct from a turn that is attempted but does not land (unclear_turn). An interlude doing its intended job is a craft choice, not this flaw.
It ends about where it started
6/10 expected
What happens here obliges what comes next
5/10 expected
The scene reaches its function and keeps going, or carries beats/lines cuttable without losing what it's there to do — waste not explained by the mechanism.
There’s avoidable waste on the page
5/10 expected
The scene/sequence shifts location, time, POV, mode, or thread without making the causal/spatial/emotional/rhythmic relationship between adjacent chunks legible.
The parts sit side by side rather than building
7/10 core
The reader can follow what matters
3/10 expected
The scene's main situation/image/beat-pattern is recognizable genre convention and the script adds no specific inversion, collision, POV, cost, world-rule, or tonal twist that changes how it plays.
It plays close to the version we’ve seen before
3/10 expected
The scene sets up its conflict then plays the most likely version — no turn, reversal, complication, or reveal the reader couldn't call in advance.
The beats can be called before they land
4/10 core
The emotion is described on the page rather than produced through the beats.
The feeling is stated more than felt
5/10 core
The unit completes its business and ends on a settled beat — no new live question, demand, or expectation is created for the next unit to inherit.
It settles at the exit rather than pulling on
This scene has been scored but its written read hasn’t been generated yet — the notes above are derived from the scores.
No explanation provided.
No explanation provided.
“Grab ‘em by the throat and never let ‘em go.”
The scene level score is the impact on the reader or audience to continue reading.
The Script score is how compelled they are to keep reading based on the rest of the script so far.
The scene ends with Namor becoming king, which feels like a natural endpoint. It doesn't create a cliffhanger or open question for the next scene, but it does deepen the reader's understanding of Namor's motivations, making future conflicts more resonant.
Given the whole script so far, this origin flashback provides crucial context for Namor's present-day actions, but it slows the momentum of the chase/rescue plot. The reader is pulled forward by the unresolved fate of Shuri and Riri, not by this scene itself.
No lens is broken, but Design and Read are soft — this reads as a polish pass.
HoldingThe reader can follow what matters.
Craft Read is the familiar battery — concept, plot, characters, dialogue, stakes, pacing.
Scene Mechanics is twelve specific ways a scene stalls — it ends about where it started, nothing is really pushing it, you can call the beats before they land — with about forty finer versions underneath them. So when a scene drags, you find out what's dragging it — not just how much.
6/10 core
It commits to one clear thing and holds it
4/10 core
The scene asserts tension/stakes/unease but no locatable page-visible force produces it — mood is mistaken for pressure (the pressure firewall).
It leans on mood instead of something actually pushing it
4/10 expected
Beats restate the same note; the reader’s experience does not change across the scene.
It restates its note rather than deepening it
5/10 core
The unit connects, displays, or frames — it never attempts to change a dramatic condition. Distinct from a turn that is attempted but does not land (unclear_turn). An interlude doing its intended job is a craft choice, not this flaw.
It ends about where it started
6/10 expected
What happens here obliges what comes next
6/10 expected
Every beat and line earns its place
6/10 expected
The parts are ordered and seamed so they build
7/10 core
The reader can follow what matters
4/10 light
It plays close to the version we’ve seen before
This scene's role doesn't owe this, so a low reading here is neutral rather than a fault.
4/10 light
The beats can be called before they land
This scene's role doesn't owe this, so a low reading here is neutral rather than a fault.
5/10 expected
The emotion is described on the page rather than produced through the beats.
The feeling is stated more than felt
6/10 expected
The exit pulls you into the next one
This scene has been scored but its written read hasn’t been generated yet — the notes above are derived from the scores.
No explanation provided.
No explanation provided.
“Grab ‘em by the throat and never let ‘em go.”
The scene level score is the impact on the reader or audience to continue reading.
The Script score is how compelled they are to keep reading based on the rest of the script so far.
The scene ends with Shuri and Namor descending into the ocean, creating a strong cliffhanger—what will Talocan look like? The reader wants to see the underwater world and learn what happens next. The open question of Riri's fate also compels continuation.
The script has built strong momentum through the chase, the attack on the bridge, and the political fallout. This scene deepens the antagonist and raises the stakes, making the reader invested in the ideological conflict. The unresolved threads (Riri's laptop, Ross's involvement, Nakia's mission) all pull forward.
No lens is broken, but Read is soft — this reads as a polish pass.
HoldingThe reader can follow what matters.
Craft Read is the familiar battery — concept, plot, characters, dialogue, stakes, pacing.
Scene Mechanics is twelve specific ways a scene stalls — it ends about where it started, nothing is really pushing it, you can call the beats before they land — with about forty finer versions underneath them. So when a scene drags, you find out what's dragging it — not just how much.
7/10 core
It commits to one clear thing and holds it
6/10 core
A real force keeps it pushing forward
6/10 core
The situation deepens as it goes
7/10 core
It turns — something is different by the end
6/10 core
What happens here obliges what comes next
5/10 expected
The scene reaches its function and keeps going, or carries beats/lines cuttable without losing what it's there to do — waste not explained by the mechanism.
There’s avoidable waste on the page
7/10 expected
The parts are ordered and seamed so they build
8/10 expected
The reader can follow what matters
5/10 expected
The scene's main situation/image/beat-pattern is recognizable genre convention and the script adds no specific inversion, collision, POV, cost, world-rule, or tonal twist that changes how it plays.
It plays close to the version we’ve seen before
5/10 expected
The scene sets up its conflict then plays the most likely version — no turn, reversal, complication, or reveal the reader couldn't call in advance.
The beats can be called before they land
6/10 expected
The feeling comes off the page
7/10 expected
The exit pulls you into the next one
This scene has been scored but its written read hasn’t been generated yet — the notes above are derived from the scores.
No explanation provided.
No explanation provided.
“Grab ‘em by the throat and never let ‘em go.”
The scene level score is the impact on the reader or audience to continue reading.
The Script score is how compelled they are to keep reading based on the rest of the script so far.
The scene ends with a cut to Ross's chloroform attack, which creates a cliffhanger but feels disconnected from the main plot. The reader may want to see what happens to Ross, but the Talocan thread is left unresolved.
The script has built strong momentum through the action and political intrigue. This scene adds depth to Namor and Talocan, but the Ross subplot feels like a detour. The reader is still compelled by Shuri's fate and the diplomatic stakes.
No lens is broken, but Design and Read are soft — this reads as a polish pass.
HoldingThe reader can follow what matters.
Craft Read is the familiar battery — concept, plot, characters, dialogue, stakes, pacing.
Scene Mechanics is twelve specific ways a scene stalls — it ends about where it started, nothing is really pushing it, you can call the beats before they land — with about forty finer versions underneath them. So when a scene drags, you find out what's dragging it — not just how much.
6/10 core
It commits to one clear thing and holds it
4/10 core
The scene asserts tension/stakes/unease but no locatable page-visible force produces it — mood is mistaken for pressure (the pressure firewall).
It leans on mood instead of something actually pushing it
4/10 expected
Beats restate the same note; the reader’s experience does not change across the scene.
It restates its note rather than deepening it
4/10 core
The unit connects, displays, or frames — it never attempts to change a dramatic condition. Distinct from a turn that is attempted but does not land (unclear_turn). An interlude doing its intended job is a craft choice, not this flaw.
It ends about where it started
6/10 expected
What happens here obliges what comes next
7/10 core
Every beat and line earns its place
6/10 expected
The parts are ordered and seamed so they build
8/10 core
The reader can follow what matters
4/10 expected
The scene's main situation/image/beat-pattern is recognizable genre convention and the script adds no specific inversion, collision, POV, cost, world-rule, or tonal twist that changes how it plays.
It plays close to the version we’ve seen before
3/10 light
The beats can be called before they land
This scene's role doesn't owe this, so a low reading here is neutral rather than a fault.
4/10 expected
The emotion is described on the page rather than produced through the beats.
The feeling is stated more than felt
6/10 core
The exit pulls you into the next one
This scene has been scored but its written read hasn’t been generated yet — the notes above are derived from the scores.
No explanation provided.
No explanation provided.
“Grab ‘em by the throat and never let ‘em go.”
The scene level score is the impact on the reader or audience to continue reading.
The Script score is how compelled they are to keep reading based on the rest of the script so far.
This scene compels continuation because it ends on a cliffhanger (the guard's look), leaving the reader wondering if Ross's cover will be blown, but the cut is abrupt.
Given the whole script, the reader is pulled to continue because of the ongoing rescue mission for Shuri and Riri, the unresolved threat from Namor, and Ross's risky infiltration; this scene adds a new thread but doesn't resolve existing ones.
All three lenses are solid — worth protecting as it stands.
HoldingThe reader can follow what matters.
Craft Read is the familiar battery — concept, plot, characters, dialogue, stakes, pacing.
Scene Mechanics is twelve specific ways a scene stalls — it ends about where it started, nothing is really pushing it, you can call the beats before they land — with about forty finer versions underneath them. So when a scene drags, you find out what's dragging it — not just how much.
7/10 core
It commits to one clear thing and holds it
6/10 core
A real force keeps it pushing forward
5/10 expected
The surface is full of events and motion, but the governing thread ends where it started — activity substitutes for evolution. Distinct from beats literally restating the same note.
It restates its note rather than deepening it
7/10 core
It turns — something is different by the end
6/10 expected
What happens here obliges what comes next
6/10 expected
Every beat and line earns its place
7/10 expected
The parts are ordered and seamed so they build
8/10 core
The reader can follow what matters
5/10 light
It plays close to the version we’ve seen before
This scene's role doesn't owe this, so a low reading here is neutral rather than a fault.
6/10 light
It defeats anticipation fairly
This scene's role doesn't owe this, so a low reading here is neutral rather than a fault.
6/10 expected
The feeling comes off the page
7/10 core
The exit pulls you into the next one
This scene has been scored but its written read hasn’t been generated yet — the notes above are derived from the scores.
No explanation provided.
No explanation provided.
“Grab ‘em by the throat and never let ‘em go.”
The scene level score is the impact on the reader or audience to continue reading.
The Script score is how compelled they are to keep reading based on the rest of the script so far.
The scene ends with Ross flushing the beads and planning the next step, creating a clear hook: will he successfully swap the laptop? The open question of the laptop's fate compels the reader to continue.
The script has strong momentum: Shuri is captured, Ramonda is desperate, and Ross is actively helping. This scene reinforces the alliance and advances the plan, keeping the reader invested in the rescue mission.
Read is broken — a load-bearing lens isn’t doing its job yet.
HoldingThe reader can follow what matters.
Craft Read is the familiar battery — concept, plot, characters, dialogue, stakes, pacing.
Scene Mechanics is twelve specific ways a scene stalls — it ends about where it started, nothing is really pushing it, you can call the beats before they land — with about forty finer versions underneath them. So when a scene drags, you find out what's dragging it — not just how much.
6/10 core
It commits to one clear thing and holds it
4/10 core
The scene asserts tension/stakes/unease but no locatable page-visible force produces it — mood is mistaken for pressure (the pressure firewall).
It leans on mood instead of something actually pushing it
4/10 expected
The surface is full of events and motion, but the governing thread ends where it started — activity substitutes for evolution. Distinct from beats literally restating the same note.
It restates its note rather than deepening it
3/10 core
The unit connects, displays, or frames — it never attempts to change a dramatic condition. Distinct from a turn that is attempted but does not land (unclear_turn). An interlude doing its intended job is a craft choice, not this flaw.
It ends about where it started
5/10 expected
The scene delivers information or understanding but no one is forced to decide or act on it.
The result doesn’t oblige what comes next
6/10 expected
Every beat and line earns its place
5/10 expected
The scene/sequence shifts location, time, POV, mode, or thread without making the causal/spatial/emotional/rhythmic relationship between adjacent chunks legible.
The parts sit side by side rather than building
7/10 core
The reader can follow what matters
3/10 light
The scene's main situation/image/beat-pattern is recognizable genre convention and the script adds no specific inversion, collision, POV, cost, world-rule, or tonal twist that changes how it plays.
It plays close to the version we’ve seen before
This scene's role doesn't owe this, so a low reading here is neutral rather than a fault.
3/10 light
The scene sets up its conflict then plays the most likely version — no turn, reversal, complication, or reveal the reader couldn't call in advance.
The beats can be called before they land
This scene's role doesn't owe this, so a low reading here is neutral rather than a fault.
4/10 expected
The emotion is described on the page rather than produced through the beats.
The feeling is stated more than felt
5/10 core
The unit completes its business and ends on a settled beat — no new live question, demand, or expectation is created for the next unit to inherit.
It settles at the exit rather than pulling on
This scene has been scored but its written read hasn’t been generated yet — the notes above are derived from the scores.
No explanation provided.
No explanation provided.
“Grab ‘em by the throat and never let ‘em go.”
The scene level score is the impact on the reader or audience to continue reading.
The Script score is how compelled they are to keep reading based on the rest of the script so far.
The scene ends with the plan in motion and Nakia's approach, creating clear suspense about whether Shuri's ruse will succeed and if Nakia will reach her in time.
Given the whole script, the momentum is strong: Shuri's escape plan, Nakia's infiltration, and Ramonda's confrontation with Namor all converge, keeping the reader invested in the multiple threads.
All three lenses are solid — worth protecting as it stands.
HoldingIt commits to one clear thing and holds it.
Craft Read is the familiar battery — concept, plot, characters, dialogue, stakes, pacing.
Scene Mechanics is twelve specific ways a scene stalls — it ends about where it started, nothing is really pushing it, you can call the beats before they land — with about forty finer versions underneath them. So when a scene drags, you find out what's dragging it — not just how much.
8/10 core
It commits to one clear thing and holds it
7/10 core
A real force keeps it pushing forward
6/10 expected
The surface is full of events and motion, but the governing thread ends where it started — activity substitutes for evolution. Distinct from beats literally restating the same note.
The situation deepens as it goes
7/10 core
It turns — something is different by the end
8/10 core
What happens here obliges what comes next
7/10 expected
Every beat and line earns its place
6/10 expected
Page space and pacing emphasize the wrong beats — the important turn is rushed/buried while minor business is lingered on.
The parts are ordered and seamed so they build
8/10 core
The reader can follow what matters
5/10 light
It plays close to the version we’ve seen before
This scene's role doesn't owe this, so a low reading here is neutral rather than a fault.
5/10 light
The beats can be called before they land
This scene's role doesn't owe this, so a low reading here is neutral rather than a fault.
7/10 expected
The feeling comes off the page
8/10 core
The exit pulls you into the next one
This scene has been scored but its written read hasn’t been generated yet — the notes above are derived from the scores.
No explanation provided.
No explanation provided.
“Grab ‘em by the throat and never let ‘em go.”
The scene level score is the impact on the reader or audience to continue reading.
The Script score is how compelled they are to keep reading based on the rest of the script so far.
This scene compels the reader to continue because it ends with Namor's ultimatum and Ramonda's failed negotiation, leaving open questions: Will Shuri accept the alliance? Will Ramonda find another way? The suspense is moderate but clear.
Given the whole script, the reader is pulled forward by the unresolved arcs: Shuri's captivity, the scientist's fate, Ross's covert mission, and Nakia's search. The scene maintains momentum but the repetitive negotiation slightly cools the urgency built earlier.
No lens is broken, but Execution and Read are soft — this reads as a polish pass.
HoldingWhat happens here obliges what comes next.
Craft Read is the familiar battery — concept, plot, characters, dialogue, stakes, pacing.
Scene Mechanics is twelve specific ways a scene stalls — it ends about where it started, nothing is really pushing it, you can call the beats before they land — with about forty finer versions underneath them. So when a scene drags, you find out what's dragging it — not just how much.
4/10 core
Several candidate threads compete and none governs — the scene splits its focus rather than committing to one determinate spine.
It isn’t clearly about one thing yet
7/10 core
A real force keeps it pushing forward
5/10 expected
Beats restate the same note; the reader’s experience does not change across the scene.
It restates its note rather than deepening it
7/10 core
It turns — something is different by the end
8/10 expected
What happens here obliges what comes next
5/10 expected
The scene reaches its function and keeps going, or carries beats/lines cuttable without losing what it's there to do — waste not explained by the mechanism.
There’s avoidable waste on the page
6/10 expected
The parts are ordered and seamed so they build
7/10 core
The reader can follow what matters
3/10 light
It plays close to the version we’ve seen before
This scene's role doesn't owe this, so a low reading here is neutral rather than a fault.
4/10 light
The beats can be called before they land
This scene's role doesn't owe this, so a low reading here is neutral rather than a fault.
6/10 expected
The feeling comes off the page
7/10 core
The exit pulls you into the next one
This scene has been scored but its written read hasn’t been generated yet — the notes above are derived from the scores.
No explanation provided.
No explanation provided.
“Grab ‘em by the throat and never let ‘em go.”
The scene level score is the impact on the reader or audience to continue reading.
The Script score is how compelled they are to keep reading based on the rest of the script so far.
This scene compels the reader to continue because the failed rescue and the killing of the guards create immediate consequences: war is now inevitable, and Shuri's moral stance is challenged. The reader wants to see how this escalates.
Given the whole script so far, the reader is pulled to continue because the stakes have been raised dramatically: Shuri is still captive, war looms, and the rescue attempt has failed. The momentum from previous scenes (Ramonda's deal, Nakia's infiltration) builds to this crisis point.
No lens is broken, but Design, Execution and Read are soft — this reads as a polish pass.
An aftermath beat lands the cost of what just happened rather than driving new action.
HoldingThe reader can follow what matters.
Craft Read is the familiar battery — concept, plot, characters, dialogue, stakes, pacing.
Scene Mechanics is twelve specific ways a scene stalls — it ends about where it started, nothing is really pushing it, you can call the beats before they land — with about forty finer versions underneath them. So when a scene drags, you find out what's dragging it — not just how much.
4/10 core
Several candidate threads compete and none governs — the scene splits its focus rather than committing to one determinate spine.
It isn’t clearly about one thing yet
6/10 core
A real force keeps it pushing forward
4/10 expected
Beats restate the same note; the reader’s experience does not change across the scene.
It restates its note rather than deepening it
5/10 core
The unit connects, displays, or frames — it never attempts to change a dramatic condition. Distinct from a turn that is attempted but does not land (unclear_turn). An interlude doing its intended job is a craft choice, not this flaw.
It ends about where it started
6/10 core
What happens here obliges what comes next
6/10 expected
Every beat and line earns its place
5/10 expected
Page space and pacing emphasize the wrong beats — the important turn is rushed/buried while minor business is lingered on.
The parts sit side by side rather than building
7/10 core
The reader can follow what matters
3/10 light
It plays close to the version we’ve seen before
This scene's role doesn't owe this, so a low reading here is neutral rather than a fault.
4/10 light
The beats can be called before they land
This scene's role doesn't owe this, so a low reading here is neutral rather than a fault.
5/10 expected
The emotion is described on the page rather than produced through the beats.
The feeling is stated more than felt
6/10 core
The exit pulls you into the next one
This scene has been scored but its written read hasn’t been generated yet — the notes above are derived from the scores.
No explanation provided.
No explanation provided.
“Grab ‘em by the throat and never let ‘em go.”
The scene level score is the impact on the reader or audience to continue reading.
The Script score is how compelled they are to keep reading based on the rest of the script so far.
This scene compels continuation through the unresolved threat of Namor's retaliation and the mystery of Okoye's demotion, but the self-contained rescue resolution slightly reduces urgency.
The script maintains strong momentum through the accumulated arcs of Shuri's captivity, Namor's threat, and the political fallout in Wakanda; this scene adds a new thread (Okoye's demotion) while resolving the rescue, keeping the reader invested.
No lens is broken, but Design, Execution and Read are soft — this reads as a polish pass.
HoldingWhat happens here obliges what comes next.
Craft Read is the familiar battery — concept, plot, characters, dialogue, stakes, pacing.
Scene Mechanics is twelve specific ways a scene stalls — it ends about where it started, nothing is really pushing it, you can call the beats before they land — with about forty finer versions underneath them. So when a scene drags, you find out what's dragging it — not just how much.
6/10 core
It commits to one clear thing and holds it
4/10 core
The scene asserts tension/stakes/unease but no locatable page-visible force produces it — mood is mistaken for pressure (the pressure firewall).
It leans on mood instead of something actually pushing it
4/10 expected
Beats restate the same note; the reader’s experience does not change across the scene.
It restates its note rather than deepening it
5/10 core
The unit connects, displays, or frames — it never attempts to change a dramatic condition. Distinct from a turn that is attempted but does not land (unclear_turn). An interlude doing its intended job is a craft choice, not this flaw.
It ends about where it started
7/10 core
What happens here obliges what comes next
6/10 expected
Every beat and line earns its place
5/10 expected
Page space and pacing emphasize the wrong beats — the important turn is rushed/buried while minor business is lingered on.
The parts sit side by side rather than building
7/10 core
The reader can follow what matters
3/10 light
The scene's main situation/image/beat-pattern is recognizable genre convention and the script adds no specific inversion, collision, POV, cost, world-rule, or tonal twist that changes how it plays.
It plays close to the version we’ve seen before
This scene's role doesn't owe this, so a low reading here is neutral rather than a fault.
3/10 light
The scene sets up its conflict then plays the most likely version — no turn, reversal, complication, or reveal the reader couldn't call in advance.
The beats can be called before they land
This scene's role doesn't owe this, so a low reading here is neutral rather than a fault.
5/10 expected
The emotion is described on the page rather than produced through the beats.
The feeling is stated more than felt
6/10 core
The exit pulls you into the next one
This scene has been scored but its written read hasn’t been generated yet — the notes above are derived from the scores.
No explanation provided.
No explanation provided.
“Grab ‘em by the throat and never let ‘em go.”
The scene level score is the impact on the reader or audience to continue reading.
The Script score is how compelled they are to keep reading based on the rest of the script so far.
This scene compels continuation by ending on a clear cliffhanger—Namor's war plan—leaving the reader eager to see the attack on Wakanda.
Given the whole script, the momentum is strong: Shuri's escape, Nakia's involvement, and now Namor's retaliation create multiple threads that pull the reader forward.
No lens is broken, but Design, Execution and Read are soft — this reads as a polish pass.
An aftermath beat lands the cost of what just happened rather than driving new action.
HoldingA real force keeps it pushing forward.
Craft Read is the familiar battery — concept, plot, characters, dialogue, stakes, pacing.
Scene Mechanics is twelve specific ways a scene stalls — it ends about where it started, nothing is really pushing it, you can call the beats before they land — with about forty finer versions underneath them. So when a scene drags, you find out what's dragging it — not just how much.
4/10 core
Several candidate threads compete and none governs — the scene splits its focus rather than committing to one determinate spine.
It isn’t clearly about one thing yet
6/10 core
A real force keeps it pushing forward
4/10 expected
Beats restate the same note; the reader’s experience does not change across the scene.
It restates its note rather than deepening it
4/10 core
The unit connects, displays, or frames — it never attempts to change a dramatic condition. Distinct from a turn that is attempted but does not land (unclear_turn). An interlude doing its intended job is a craft choice, not this flaw.
It ends about where it started
6/10 expected
What happens here obliges what comes next
5/10 expected
The scene reaches its function and keeps going, or carries beats/lines cuttable without losing what it's there to do — waste not explained by the mechanism.
There’s avoidable waste on the page
4/10 expected
The scene/sequence shifts location, time, POV, mode, or thread without making the causal/spatial/emotional/rhythmic relationship between adjacent chunks legible.
The parts sit side by side rather than building
6/10 core
The reader can follow what matters
4/10 light
It plays close to the version we’ve seen before
This scene's role doesn't owe this, so a low reading here is neutral rather than a fault.
4/10 light
The beats can be called before they land
This scene's role doesn't owe this, so a low reading here is neutral rather than a fault.
5/10 expected
The emotion is described on the page rather than produced through the beats.
The feeling is stated more than felt
5/10 expected
The unit completes its business and ends on a settled beat — no new live question, demand, or expectation is created for the next unit to inherit.
It settles at the exit rather than pulling on
This scene has been scored but its written read hasn’t been generated yet — the notes above are derived from the scores.
No explanation provided.
No explanation provided.
“Grab ‘em by the throat and never let ‘em go.”
The scene level score is the impact on the reader or audience to continue reading.
The Script score is how compelled they are to keep reading based on the rest of the script so far.
This scene compels continuation through the looming threat of Namor and the unresolved bracelet symbol, but the fragmented structure slightly dampens urgency.
Given the whole script, the accumulated momentum from Namor's betrayal and Shuri's escape keeps the reader invested, though this scene's slower pace provides a breather that risks losing tension.
All three lenses are solid — worth protecting as it stands.
HoldingThe reader can follow what matters.
Craft Read is the familiar battery — concept, plot, characters, dialogue, stakes, pacing.
Scene Mechanics is twelve specific ways a scene stalls — it ends about where it started, nothing is really pushing it, you can call the beats before they land — with about forty finer versions underneath them. So when a scene drags, you find out what's dragging it — not just how much.
7/10 core
It commits to one clear thing and holds it
6/10 expected
A real force keeps it pushing forward
7/10 expected
The situation deepens as it goes
7/10 core
It turns — something is different by the end
7/10 expected
What happens here obliges what comes next
6/10 expected
Every beat and line earns its place
7/10 expected
The parts are ordered and seamed so they build
8/10 core
The reader can follow what matters
5/10 expected
It plays close to the version we’ve seen before
5/10 expected
The beats can be called before they land
8/10 core
The feeling comes off the page
8/10 core
The exit pulls you into the next one
This scene has been scored but its written read hasn’t been generated yet — the notes above are derived from the scores.
No explanation provided.
No explanation provided.
“Grab ‘em by the throat and never let ‘em go.”
The scene level score is the impact on the reader or audience to continue reading.
The Script score is how compelled they are to keep reading based on the rest of the script so far.
The scene compels continuation because the flood raises immediate questions about the attack's source and scale, but the self-contained dialogue moment slightly reduces urgency.
Given the whole script, the reader is pulled forward by the unresolved threat of Namor's retaliation and the emotional arcs of Okoye and Nakia, though the pacing here is a minor drag.
No lens is broken, but Design, Execution and Read are soft — this reads as a polish pass.
An aftermath beat lands the cost of what just happened rather than driving new action.
HoldingThe reader can follow what matters.
Craft Read is the familiar battery — concept, plot, characters, dialogue, stakes, pacing.
Scene Mechanics is twelve specific ways a scene stalls — it ends about where it started, nothing is really pushing it, you can call the beats before they land — with about forty finer versions underneath them. So when a scene drags, you find out what's dragging it — not just how much.
4/10 core
Several candidate threads compete and none governs — the scene splits its focus rather than committing to one determinate spine.
It isn’t clearly about one thing yet
6/10 core
A real force keeps it pushing forward
4/10 expected
The surface is full of events and motion, but the governing thread ends where it started — activity substitutes for evolution. Distinct from beats literally restating the same note.
It restates its note rather than deepening it
5/10 core
The unit connects, displays, or frames — it never attempts to change a dramatic condition. Distinct from a turn that is attempted but does not land (unclear_turn). An interlude doing its intended job is a craft choice, not this flaw.
It ends about where it started
6/10 expected
What happens here obliges what comes next
6/10 expected
Every beat and line earns its place
5/10 expected
The scene/sequence shifts location, time, POV, mode, or thread without making the causal/spatial/emotional/rhythmic relationship between adjacent chunks legible.
The parts sit side by side rather than building
7/10 core
The reader can follow what matters
4/10 light
It plays close to the version we’ve seen before
This scene's role doesn't owe this, so a low reading here is neutral rather than a fault.
4/10 light
The beats can be called before they land
This scene's role doesn't owe this, so a low reading here is neutral rather than a fault.
6/10 expected
The feeling comes off the page
6/10 expected
The exit pulls you into the next one
This scene has been scored but its written read hasn’t been generated yet — the notes above are derived from the scores.
No explanation provided.
No explanation provided.
“Grab ‘em by the throat and never let ‘em go.”
The scene level score is the impact on the reader or audience to continue reading.
The Script score is how compelled they are to keep reading based on the rest of the script so far.
This scene compels continuation due to the unresolved attack and cliffhanger of the sirens, but the fragmented structure slightly reduces urgency.
Given the whole script, the attack on Wakanda raises stakes and hooks the reader, but the cumulative momentum is slightly slowed by the scene's disjointed nature.
Read is broken — a load-bearing lens isn’t doing its job yet.
HoldingA real force keeps it pushing forward.
Craft Read is the familiar battery — concept, plot, characters, dialogue, stakes, pacing.
Scene Mechanics is twelve specific ways a scene stalls — it ends about where it started, nothing is really pushing it, you can call the beats before they land — with about forty finer versions underneath them. So when a scene drags, you find out what's dragging it — not just how much.
4/10 core
Several candidate threads compete and none governs — the scene splits its focus rather than committing to one determinate spine.
It isn’t clearly about one thing yet
6/10 core
A real force keeps it pushing forward
4/10 expected
The surface is full of events and motion, but the governing thread ends where it started — activity substitutes for evolution. Distinct from beats literally restating the same note.
It restates its note rather than deepening it
4/10 core
The unit connects, displays, or frames — it never attempts to change a dramatic condition. Distinct from a turn that is attempted but does not land (unclear_turn). An interlude doing its intended job is a craft choice, not this flaw.
It ends about where it started
5/10 expected
The result doesn’t oblige what comes next
4/10 expected
The scene reaches its function and keeps going, or carries beats/lines cuttable without losing what it's there to do — waste not explained by the mechanism.
There’s avoidable waste on the page
4/10 expected
Page space and pacing emphasize the wrong beats — the important turn is rushed/buried while minor business is lingered on.
The parts sit side by side rather than building
6/10 core
The reader can follow what matters
3/10 light
It plays close to the version we’ve seen before
This scene's role doesn't owe this, so a low reading here is neutral rather than a fault.
3/10 light
The beats can be called before they land
This scene's role doesn't owe this, so a low reading here is neutral rather than a fault.
5/10 expected
The feeling is stated more than felt
5/10 expected
It settles at the exit rather than pulling on
This scene has been scored but its written read hasn’t been generated yet — the notes above are derived from the scores.
No explanation provided.
No explanation provided.
“Grab ‘em by the throat and never let ‘em go.”
The scene level score is the impact on the reader or audience to continue reading.
The Script score is how compelled they are to keep reading based on the rest of the script so far.
This scene compels the reader to continue because the attack is unresolved, Namor is advancing on the palace, and multiple characters are in peril, creating strong cliffhangers.
Given the whole script, the attack on Wakanda is a major escalation that pays off the buildup of Talocan as a threat; the reader is pulled forward by the need to see the outcome and the fates of key characters like Shuri and Ramonda.
No lens is broken, but Design, Execution and Read are soft — this reads as a polish pass.
HoldingA real force keeps it pushing forward.
Craft Read is the familiar battery — concept, plot, characters, dialogue, stakes, pacing.
Scene Mechanics is twelve specific ways a scene stalls — it ends about where it started, nothing is really pushing it, you can call the beats before they land — with about forty finer versions underneath them. So when a scene drags, you find out what's dragging it — not just how much.
4/10 core
Several candidate threads compete and none governs — the scene splits its focus rather than committing to one determinate spine.
It isn’t clearly about one thing yet
6/10 core
A real force keeps it pushing forward
4/10 expected
The surface is full of events and motion, but the governing thread ends where it started — activity substitutes for evolution. Distinct from beats literally restating the same note.
It restates its note rather than deepening it
4/10 core
The unit connects, displays, or frames — it never attempts to change a dramatic condition. Distinct from a turn that is attempted but does not land (unclear_turn). An interlude doing its intended job is a craft choice, not this flaw.
It ends about where it started
6/10 expected
What happens here obliges what comes next
5/10 expected
The scene reaches its function and keeps going, or carries beats/lines cuttable without losing what it's there to do — waste not explained by the mechanism.
There’s avoidable waste on the page
5/10 expected
Page space and pacing emphasize the wrong beats — the important turn is rushed/buried while minor business is lingered on.
The parts sit side by side rather than building
6/10 core
The reader can follow what matters
3/10 light
It plays close to the version we’ve seen before
This scene's role doesn't owe this, so a low reading here is neutral rather than a fault.
3/10 light
The beats can be called before they land
This scene's role doesn't owe this, so a low reading here is neutral rather than a fault.
5/10 expected
The feeling is stated more than felt
6/10 core
The exit pulls you into the next one
This scene has been scored but its written read hasn’t been generated yet — the notes above are derived from the scores.
No explanation provided.
No explanation provided.
“Grab ‘em by the throat and never let ‘em go.”
The scene level score is the impact on the reader or audience to continue reading.
The Script score is how compelled they are to keep reading based on the rest of the script so far.
This scene ends on a cliffhanger with Namor attacking the Tribal Council windows, Ramonda and Riri in danger, and Shuri's fate uncertain, compelling the reader to continue.
The script has built strong momentum with the invasion, character arcs (Shuri's growth, Ramonda's leadership), and unresolved conflicts (Namor's threat, Riri's safety), making the reader eager to see the resolution.
All three lenses are solid — worth protecting as it stands.
An aftermath beat lands the cost of what just happened rather than driving new action.
HoldingWhat happens here obliges what comes next.
Craft Read is the familiar battery — concept, plot, characters, dialogue, stakes, pacing.
Scene Mechanics is twelve specific ways a scene stalls — it ends about where it started, nothing is really pushing it, you can call the beats before they land — with about forty finer versions underneath them. So when a scene drags, you find out what's dragging it — not just how much.
7/10 core
It commits to one clear thing and holds it
8/10 core
A real force keeps it pushing forward
6/10 expected
The situation deepens as it goes
8/10 core
It turns — something is different by the end
9/10 core
What happens here obliges what comes next
6/10 expected
The scene reaches its function and keeps going, or carries beats/lines cuttable without losing what it's there to do — waste not explained by the mechanism.
Every beat and line earns its place
7/10 expected
The parts are ordered and seamed so they build
8/10 core
The reader can follow what matters
4/10 light
It plays close to the version we’ve seen before
This scene's role doesn't owe this, so a low reading here is neutral rather than a fault.
5/10 light
The beats can be called before they land
This scene's role doesn't owe this, so a low reading here is neutral rather than a fault.
8/10 core
The feeling comes off the page
9/10 core
The exit pulls you into the next one
This scene has been scored but its written read hasn’t been generated yet — the notes above are derived from the scores.
No explanation provided.
No explanation provided.
“Grab ‘em by the throat and never let ‘em go.”
The scene level score is the impact on the reader or audience to continue reading.
The Script score is how compelled they are to keep reading based on the rest of the script so far.
This scene creates a massive cliffhanger with the death of the queen and Namor's one-week ultimatum. The reader is compelled to immediately see the aftermath and how Shuri will respond to this devastating loss.
The script has built immense momentum. The attack on Wakanda and the death of Ramonda are the culmination of the central conflict. The reader is now deeply invested in Shuri's journey of grief and vengeance, and the promise of a final confrontation with Namor is a powerful hook.
No lens is broken, but Read is soft — this reads as a polish pass.
An aftermath beat lands the cost of what just happened rather than driving new action.
HoldingThe reader can follow what matters.
Craft Read is the familiar battery — concept, plot, characters, dialogue, stakes, pacing.
Scene Mechanics is twelve specific ways a scene stalls — it ends about where it started, nothing is really pushing it, you can call the beats before they land — with about forty finer versions underneath them. So when a scene drags, you find out what's dragging it — not just how much.
6/10 core
It commits to one clear thing and holds it
7/10 core
A real force keeps it pushing forward
5/10 expected
Beats restate the same note; the reader’s experience does not change across the scene.
It restates its note rather than deepening it
7/10 core
It turns — something is different by the end
6/10 expected
What happens here obliges what comes next
6/10 expected
Every beat and line earns its place
6/10 expected
The parts are ordered and seamed so they build
8/10 core
The reader can follow what matters
3/10 expected
The scene's main situation/image/beat-pattern is recognizable genre convention and the script adds no specific inversion, collision, POV, cost, world-rule, or tonal twist that changes how it plays.
It plays close to the version we’ve seen before
3/10 light
The beats can be called before they land
This scene's role doesn't owe this, so a low reading here is neutral rather than a fault.
7/10 core
The feeling comes off the page
6/10 core
The exit pulls you into the next one
This scene has been scored but its written read hasn’t been generated yet — the notes above are derived from the scores.
No explanation provided.
No explanation provided.
“Grab ‘em by the throat and never let ‘em go.”
The scene level score is the impact on the reader or audience to continue reading.
The Script score is how compelled they are to keep reading based on the rest of the script so far.
The scene ends with Shuri in Nakia's arms, a moment of fragile hope. It compels the reader to continue because Shuri's emotional state is still precarious, and the funeral scene (207) is clearly next, promising further exploration of her grief.
Given the whole script, the reader is pulled forward by the unresolved war with Talocan, Ramonda's death, and Shuri's now-fragile will to live. This scene deepens the emotional stakes, making the coming confrontation with Namor more resonant. The momentum is strong.
All three lenses are solid — worth protecting as it stands.
HoldingThe reader can follow what matters.
Craft Read is the familiar battery — concept, plot, characters, dialogue, stakes, pacing.
Scene Mechanics is twelve specific ways a scene stalls — it ends about where it started, nothing is really pushing it, you can call the beats before they land — with about forty finer versions underneath them. So when a scene drags, you find out what's dragging it — not just how much.
7/10 core
It commits to one clear thing and holds it
6/10 core
A real force keeps it pushing forward
6/10 expected
The situation deepens as it goes
7/10 core
It turns — something is different by the end
7/10 expected
What happens here obliges what comes next
7/10 expected
Every beat and line earns its place
7/10 expected
The parts are ordered and seamed so they build
8/10 core
The reader can follow what matters
5/10 light
It plays close to the version we’ve seen before
This scene's role doesn't owe this, so a low reading here is neutral rather than a fault.
5/10 light
The beats can be called before they land
This scene's role doesn't owe this, so a low reading here is neutral rather than a fault.
7/10 core
The feeling comes off the page
7/10 core
The exit pulls you into the next one
This scene has been scored but its written read hasn’t been generated yet — the notes above are derived from the scores.
No explanation provided.
No explanation provided.
“Grab ‘em by the throat and never let ‘em go.”
The scene level score is the impact on the reader or audience to continue reading.
The Script score is how compelled they are to keep reading based on the rest of the script so far.
The scene ends with Shuri's declaration of vengeance, which creates a clear hook for the next scene (how will she pursue it?), but the scene itself is self-contained.
The script has strong momentum from the attack and Ramonda's death, and this scene deepens Shuri's character arc, maintaining reader investment in her journey.
No lens is broken, but Design, Execution and Read are soft — this reads as a polish pass.
HoldingWhat happens here obliges what comes next.
Craft Read is the familiar battery — concept, plot, characters, dialogue, stakes, pacing.
Scene Mechanics is twelve specific ways a scene stalls — it ends about where it started, nothing is really pushing it, you can call the beats before they land — with about forty finer versions underneath them. So when a scene drags, you find out what's dragging it — not just how much.
4/10 core
Several candidate threads compete and none governs — the scene splits its focus rather than committing to one determinate spine.
It isn’t clearly about one thing yet
4/10 core
The scene asserts tension/stakes/unease but no locatable page-visible force produces it — mood is mistaken for pressure (the pressure firewall).
It leans on mood instead of something actually pushing it
4/10 expected
Beats restate the same note; the reader’s experience does not change across the scene.
It restates its note rather than deepening it
5/10 core
It ends about where it started
6/10 expected
What happens here obliges what comes next
5/10 expected
The scene reaches its function and keeps going, or carries beats/lines cuttable without losing what it's there to do — waste not explained by the mechanism.
There’s avoidable waste on the page
5/10 expected
Page space and pacing emphasize the wrong beats — the important turn is rushed/buried while minor business is lingered on.
The parts sit side by side rather than building
6/10 core
The reader can follow what matters
4/10 light
It plays close to the version we’ve seen before
This scene's role doesn't owe this, so a low reading here is neutral rather than a fault.
4/10 light
The beats can be called before they land
This scene's role doesn't owe this, so a low reading here is neutral rather than a fault.
5/10 expected
The emotion is described on the page rather than produced through the beats.
The feeling is stated more than felt
6/10 core
The exit pulls you into the next one
This scene has been scored but its written read hasn’t been generated yet — the notes above are derived from the scores.
No explanation provided.
No explanation provided.
“Grab ‘em by the throat and never let ‘em go.”
The scene level score is the impact on the reader or audience to continue reading.
The Script score is how compelled they are to keep reading based on the rest of the script so far.
The scene ends with the elders thinking, which is a soft pause. It doesn't create a strong cliffhanger, but the unresolved political tension and the mention of Shuri working on new technology create mild curiosity about what happens next.
Given the whole script, the momentum is still strong from the attack and Ramonda's death. The political infighting adds a new layer of tension, but the scene itself doesn't accelerate the plot significantly. The reader is likely to continue out of investment in the larger story rather than this scene's hook.
No lens is broken, but Design and Read are soft — this reads as a polish pass.
HoldingThe reader can follow what matters.
Craft Read is the familiar battery — concept, plot, characters, dialogue, stakes, pacing.
Scene Mechanics is twelve specific ways a scene stalls — it ends about where it started, nothing is really pushing it, you can call the beats before they land — with about forty finer versions underneath them. So when a scene drags, you find out what's dragging it — not just how much.
6/10 core
It commits to one clear thing and holds it
4/10 core
The scene asserts tension/stakes/unease but no locatable page-visible force produces it — mood is mistaken for pressure (the pressure firewall).
It leans on mood instead of something actually pushing it
4/10 expected
Beats restate the same note; the reader’s experience does not change across the scene.
It restates its note rather than deepening it
5/10 core
The unit connects, displays, or frames — it never attempts to change a dramatic condition. Distinct from a turn that is attempted but does not land (unclear_turn). An interlude doing its intended job is a craft choice, not this flaw.
It ends about where it started
7/10 core
What happens here obliges what comes next
7/10 expected
Every beat and line earns its place
6/10 expected
The parts are ordered and seamed so they build
8/10 core
The reader can follow what matters
3/10 light
It plays close to the version we’ve seen before
This scene's role doesn't owe this, so a low reading here is neutral rather than a fault.
4/10 light
The beats can be called before they land
This scene's role doesn't owe this, so a low reading here is neutral rather than a fault.
5/10 expected
The emotion is described on the page rather than produced through the beats.
The feeling is stated more than felt
7/10 core
The exit pulls you into the next one
This scene has been scored but its written read hasn’t been generated yet — the notes above are derived from the scores.
No explanation provided.
No explanation provided.
“Grab ‘em by the throat and never let ‘em go.”
The scene level score is the impact on the reader or audience to continue reading.
The Script score is how compelled they are to keep reading based on the rest of the script so far.
The scene ends with a clear hook—Ross must now deal with the CIA—but it feels self-contained and doesn't create a strong cliffhanger.
Given the whole script, the death of Ramonda and Shuri's new resolve are major threads, but this scene is a brief update that doesn't add much momentum.
All three lenses are solid — worth protecting as it stands.
HoldingThe reader can follow what matters.
Craft Read is the familiar battery — concept, plot, characters, dialogue, stakes, pacing.
Scene Mechanics is twelve specific ways a scene stalls — it ends about where it started, nothing is really pushing it, you can call the beats before they land — with about forty finer versions underneath them. So when a scene drags, you find out what's dragging it — not just how much.
7/10 core
It commits to one clear thing and holds it
6/10 core
A real force keeps it pushing forward
6/10 expected
The situation deepens as it goes
6/10 core
It turns — something is different by the end
7/10 core
What happens here obliges what comes next
7/10 expected
Every beat and line earns its place
7/10 expected
The parts are ordered and seamed so they build
8/10 core
The reader can follow what matters
5/10 light
It plays close to the version we’ve seen before
This scene's role doesn't owe this, so a low reading here is neutral rather than a fault.
5/10 light
The beats can be called before they land
This scene's role doesn't owe this, so a low reading here is neutral rather than a fault.
6/10 expected
The feeling comes off the page
7/10 core
The exit pulls you into the next one
This scene has been scored but its written read hasn’t been generated yet — the notes above are derived from the scores.
No explanation provided.
No explanation provided.
“Grab ‘em by the throat and never let ‘em go.”
The scene level score is the impact on the reader or audience to continue reading.
The Script score is how compelled they are to keep reading based on the rest of the script so far.
The scene ends with Ross walking back to the building, leaving the reader wondering if he'll be able to delay the attack, creating suspense.
Given the whole script, the U.S. threat adds a new layer of danger on top of Namor's attack, keeping momentum high and pulling the reader forward.
No lens is broken, but Design, Execution and Read are soft — this reads as a polish pass.
A montage compresses time. It isn’t built to turn on a single thread.
HoldingThe reader can follow what matters.
Craft Read is the familiar battery — concept, plot, characters, dialogue, stakes, pacing.
Scene Mechanics is twelve specific ways a scene stalls — it ends about where it started, nothing is really pushing it, you can call the beats before they land — with about forty finer versions underneath them. So when a scene drags, you find out what's dragging it — not just how much.
6/10 core
It commits to one clear thing and holds it
4/10 core
The scene asserts tension/stakes/unease but no locatable page-visible force produces it — mood is mistaken for pressure (the pressure firewall).
It leans on mood instead of something actually pushing it
4/10 expected
The surface is full of events and motion, but the governing thread ends where it started — activity substitutes for evolution. Distinct from beats literally restating the same note.
It restates its note rather than deepening it
3/10 core
The unit connects, displays, or frames — it never attempts to change a dramatic condition. Distinct from a turn that is attempted but does not land (unclear_turn). An interlude doing its intended job is a craft choice, not this flaw.
It ends about where it started
5/10 expected
The scene delivers information or understanding but no one is forced to decide or act on it.
The result doesn’t oblige what comes next
6/10 core
Every beat and line earns its place
5/10 core
The scene/sequence shifts location, time, POV, mode, or thread without making the causal/spatial/emotional/rhythmic relationship between adjacent chunks legible.
The parts sit side by side rather than building
7/10 core
The reader can follow what matters
4/10 expected
The scene's main situation/image/beat-pattern is recognizable genre convention and the script adds no specific inversion, collision, POV, cost, world-rule, or tonal twist that changes how it plays.
It plays close to the version we’ve seen before
3/10 expected
The scene sets up its conflict then plays the most likely version — no turn, reversal, complication, or reveal the reader couldn't call in advance.
The beats can be called before they land
5/10 expected
The emotion is described on the page rather than produced through the beats.
The feeling is stated more than felt
5/10 core
The unit completes its business and ends on a settled beat — no new live question, demand, or expectation is created for the next unit to inherit.
It settles at the exit rather than pulling on
This scene has been scored but its written read hasn’t been generated yet — the notes above are derived from the scores.
No explanation provided.
No explanation provided.
“Grab ‘em by the throat and never let ‘em go.”
The scene level score is the impact on the reader or audience to continue reading.
The Script score is how compelled they are to keep reading based on the rest of the script so far.
The scene ends with Shuri declaring 'Immediately,' creating a strong hook that makes the reader want to see the results of her work and the coming battle. The open question of whether she will succeed in becoming the Black Panther drives continuation.
Given the entire script, the momentum is high: Ramonda's death, Shuri's grief, and the threat of Namor's attack have built significant stakes. This scene channels that momentum into preparation, keeping the reader invested in the resolution.
All three lenses are solid — worth protecting as it stands.
A ritual beat repeats a known pattern on purpose, so movement and freshness read low by design.
HoldingThe reader can follow what matters.
Craft Read is the familiar battery — concept, plot, characters, dialogue, stakes, pacing.
Scene Mechanics is twelve specific ways a scene stalls — it ends about where it started, nothing is really pushing it, you can call the beats before they land — with about forty finer versions underneath them. So when a scene drags, you find out what's dragging it — not just how much.
8/10 core
It commits to one clear thing and holds it
7/10 core
A real force keeps it pushing forward
7/10 core
The situation deepens as it goes
8/10 core
It turns — something is different by the end
7/10 core
What happens here obliges what comes next
7/10 expected
Every beat and line earns its place
8/10 expected
The parts are ordered and seamed so they build
9/10 expected
The reader can follow what matters
6/10 expected
The scene's main situation/image/beat-pattern is recognizable genre convention and the script adds no specific inversion, collision, POV, cost, world-rule, or tonal twist that changes how it plays.
It’s a fresh take on this kind of scene
6/10 expected
The scene sets up its conflict then plays the most likely version — no turn, reversal, complication, or reveal the reader couldn't call in advance.
It defeats anticipation fairly
8/10 expected
The feeling comes off the page
8/10 expected
The exit pulls you into the next one
This scene has been scored but its written read hasn’t been generated yet — the notes above are derived from the scores.
No explanation provided.
No explanation provided.
“Grab ‘em by the throat and never let ‘em go.”
The scene level score is the impact on the reader or audience to continue reading.
The Script score is how compelled they are to keep reading based on the rest of the script so far.
The scene ends with Shuri awakening underwater in the Ancestral Plane, a strong cliffhanger that compels the reader to continue to see what happens next.
Given the script's momentum—Shuri's transformation, the unresolved threat of Namor, and the political tensions—this scene raises the stakes and deepens character investment, strongly pulling the reader forward.
All three lenses are solid — worth protecting as it stands.
HoldingThe reader can follow what matters.
Craft Read is the familiar battery — concept, plot, characters, dialogue, stakes, pacing.
Scene Mechanics is twelve specific ways a scene stalls — it ends about where it started, nothing is really pushing it, you can call the beats before they land — with about forty finer versions underneath them. So when a scene drags, you find out what's dragging it — not just how much.
7/10 core
It commits to one clear thing and holds it
7/10 core
A real force keeps it pushing forward
6/10 expected
The situation deepens as it goes
7/10 core
It turns — something is different by the end
7/10 expected
What happens here obliges what comes next
6/10 expected
Every beat and line earns its place
6/10 expected
The parts are ordered and seamed so they build
8/10 core
The reader can follow what matters
5/10 expected
The scene's main situation/image/beat-pattern is recognizable genre convention and the script adds no specific inversion, collision, POV, cost, world-rule, or tonal twist that changes how it plays.
It plays close to the version we’ve seen before
5/10 expected
The scene sets up its conflict then plays the most likely version — no turn, reversal, complication, or reveal the reader couldn't call in advance.
The beats can be called before they land
7/10 core
The feeling comes off the page
7/10 core
The exit pulls you into the next one
This scene has been scored but its written read hasn’t been generated yet — the notes above are derived from the scores.
No explanation provided.
No explanation provided.
“Grab ‘em by the throat and never let ‘em go.”
The scene level score is the impact on the reader or audience to continue reading.
The Script score is how compelled they are to keep reading based on the rest of the script so far.
The scene ends with Shuri's vow to kill Namor, creating a strong cliffhanger about whether she will succeed and what she will become. The reader is compelled to see the consequences.
The script has built significant momentum through the attack on Wakanda and Ramonda's death. This scene deepens Shuri's character arc and raises the stakes for the final act, keeping the reader invested.
All three lenses are solid — worth protecting as it stands.
A ritual beat repeats a known pattern on purpose, so movement and freshness read low by design.
HoldingA real force keeps it pushing forward.
Craft Read is the familiar battery — concept, plot, characters, dialogue, stakes, pacing.
Scene Mechanics is twelve specific ways a scene stalls — it ends about where it started, nothing is really pushing it, you can call the beats before they land — with about forty finer versions underneath them. So when a scene drags, you find out what's dragging it — not just how much.
6/10 core
It commits to one clear thing and holds it
7/10 core
A real force keeps it pushing forward
5/10 expected
Beats restate the same note; the reader’s experience does not change across the scene.
It restates its note rather than deepening it
7/10 core
It turns — something is different by the end
6/10 expected
What happens here obliges what comes next
5/10 expected
The scene reaches its function and keeps going, or carries beats/lines cuttable without losing what it's there to do — waste not explained by the mechanism.
There’s avoidable waste on the page
6/10 expected
The parts are ordered and seamed so they build
7/10 core
The reader can follow what matters
4/10 light
It plays close to the version we’ve seen before
This scene's role doesn't owe this, so a low reading here is neutral rather than a fault.
4/10 light
The beats can be called before they land
This scene's role doesn't owe this, so a low reading here is neutral rather than a fault.
7/10 core
The feeling comes off the page
7/10 core
The exit pulls you into the next one
This scene has been scored but its written read hasn’t been generated yet — the notes above are derived from the scores.
No explanation provided.
No explanation provided.
“Grab ‘em by the throat and never let ‘em go.”
The scene level score is the impact on the reader or audience to continue reading.
The Script score is how compelled they are to keep reading based on the rest of the script so far.
The scene ends on a triumphant note with the elders cheering, which provides closure but also sets up the next phase of the story (Shuri as Black Panther). The reader is compelled to continue to see how she will use her new role against Namor.
Given the whole script, the momentum is strong: Shuri has just become the Black Panther, the conflict with Namor is unresolved, and the fate of Wakanda hangs in the balance. The scene reinforces the central arc and raises anticipation for the final confrontation.
All three lenses are solid — worth protecting as it stands.
HoldingThe reader can follow what matters.
Craft Read is the familiar battery — concept, plot, characters, dialogue, stakes, pacing.
Scene Mechanics is twelve specific ways a scene stalls — it ends about where it started, nothing is really pushing it, you can call the beats before they land — with about forty finer versions underneath them. So when a scene drags, you find out what's dragging it — not just how much.
7/10 core
It commits to one clear thing and holds it
6/10 core
A real force keeps it pushing forward
7/10 core
The situation deepens as it goes
7/10 core
It turns — something is different by the end
7/10 expected
What happens here obliges what comes next
6/10 expected
Every beat and line earns its place
7/10 expected
The parts are ordered and seamed so they build
8/10 core
The reader can follow what matters
5/10 light
It plays close to the version we’ve seen before
This scene's role doesn't owe this, so a low reading here is neutral rather than a fault.
5/10 light
The beats can be called before they land
This scene's role doesn't owe this, so a low reading here is neutral rather than a fault.
7/10 core
The feeling comes off the page
7/10 core
The exit pulls you into the next one
This scene has been scored but its written read hasn’t been generated yet — the notes above are derived from the scores.
No explanation provided.
No explanation provided.
“Grab ‘em by the throat and never let ‘em go.”
The scene level score is the impact on the reader or audience to continue reading.
The Script score is how compelled they are to keep reading based on the rest of the script so far.
The scene ends with Shuri walking out, leaving the plan in motion and the moral question unresolved. This creates a strong hook to see if she will follow through and how M'Baku's argument will affect her.
The script has built significant momentum through the attack, Ramonda's death, and Shuri's transformation. This scene deepens the philosophical stakes and keeps the reader invested in Shuri's journey and the coming confrontation.
No lens is broken, but Design, Execution and Read are soft — this reads as a polish pass.
HoldingThe reader can follow what matters.
Craft Read is the familiar battery — concept, plot, characters, dialogue, stakes, pacing.
Scene Mechanics is twelve specific ways a scene stalls — it ends about where it started, nothing is really pushing it, you can call the beats before they land — with about forty finer versions underneath them. So when a scene drags, you find out what's dragging it — not just how much.
4/10 core
Several candidate threads compete and none governs — the scene splits its focus rather than committing to one determinate spine.
It isn’t clearly about one thing yet
4/10 core
The scene asserts tension/stakes/unease but no locatable page-visible force produces it — mood is mistaken for pressure (the pressure firewall).
It leans on mood instead of something actually pushing it
4/10 expected
Beats restate the same note; the reader’s experience does not change across the scene.
It restates its note rather than deepening it
5/10 core
The unit connects, displays, or frames — it never attempts to change a dramatic condition. Distinct from a turn that is attempted but does not land (unclear_turn). An interlude doing its intended job is a craft choice, not this flaw.
It ends about where it started
6/10 expected
What happens here obliges what comes next
6/10 expected
Every beat and line earns its place
5/10 expected
The scene/sequence shifts location, time, POV, mode, or thread without making the causal/spatial/emotional/rhythmic relationship between adjacent chunks legible.
The parts sit side by side rather than building
7/10 core
The reader can follow what matters
4/10 light
It plays close to the version we’ve seen before
This scene's role doesn't owe this, so a low reading here is neutral rather than a fault.
4/10 light
The beats can be called before they land
This scene's role doesn't owe this, so a low reading here is neutral rather than a fault.
5/10 expected
The emotion is described on the page rather than produced through the beats.
The feeling is stated more than felt
6/10 core
The exit pulls you into the next one
This scene has been scored but its written read hasn’t been generated yet — the notes above are derived from the scores.
No explanation provided.
No explanation provided.
“Grab ‘em by the throat and never let ‘em go.”
The scene level score is the impact on the reader or audience to continue reading.
The Script score is how compelled they are to keep reading based on the rest of the script so far.
This scene compels the reader to continue because the ambush has just begun, and the outcome is unresolved—Namor is under attack but not defeated, creating immediate suspense.
Given the whole script, the reader is pulled to continue because the final confrontation with Namor is now underway, and Shuri's internal conflict (vengeance vs. protection) remains unresolved. The momentum from the previous scenes (Ramonda's death, Shuri's transformation) carries forward, though this scene itself adds little new emotional fuel.
Design is broken — a load-bearing lens isn’t doing its job yet.
HoldingEvery beat and line earns its place.
Craft Read is the familiar battery — concept, plot, characters, dialogue, stakes, pacing.
Scene Mechanics is twelve specific ways a scene stalls — it ends about where it started, nothing is really pushing it, you can call the beats before they land — with about forty finer versions underneath them. So when a scene drags, you find out what's dragging it — not just how much.
4/10 core
For most of the scene the POV observes activity with no visible intention, scene question, threat, pursuit, or decision organizing what the reader is meant to track.
It isn’t clearly about one thing yet
5/10 core
It leans on mood instead of something actually pushing it
2/10 expected
The surface is full of events and motion, but the governing thread ends where it started — activity substitutes for evolution. Distinct from beats literally restating the same note.
It restates its note rather than deepening it
3/10 core
The unit connects, displays, or frames — it never attempts to change a dramatic condition. Distinct from a turn that is attempted but does not land (unclear_turn). An interlude doing its intended job is a craft choice, not this flaw.
It ends about where it started
5/10 expected
The result doesn’t oblige what comes next
6/10 expected
Every beat and line earns its place
5/10 expected
The parts sit side by side rather than building
6/10 core
The reader can follow what matters
3/10 light
It plays close to the version we’ve seen before
This scene's role doesn't owe this, so a low reading here is neutral rather than a fault.
3/10 light
The beats can be called before they land
This scene's role doesn't owe this, so a low reading here is neutral rather than a fault.
4/10 expected
The emotion is described on the page rather than produced through the beats.
The feeling is stated more than felt
5/10 core
It settles at the exit rather than pulling on
This scene has been scored but its written read hasn’t been generated yet — the notes above are derived from the scores.
No explanation provided.
No explanation provided.
“Grab ‘em by the throat and never let ‘em go.”
The scene level score is the impact on the reader or audience to continue reading.
The Script score is how compelled they are to keep reading based on the rest of the script so far.
This scene compels the reader to continue because it ends with Namor flying up with a conch shell, an action that clearly sets up his next move. The open question is what he will do with it, creating suspense for the next scene.
Given the whole script, the reader is pulled to continue because the battle is escalating, Shuri's plan is in motion, and Namor's counterattack is imminent. The momentum from previous scenes (the ambush setup, Shuri's transformation) carries forward strongly.
No lens is broken, but Design, Execution and Read are soft — this reads as a polish pass.
HoldingA real force keeps it pushing forward.
Craft Read is the familiar battery — concept, plot, characters, dialogue, stakes, pacing.
Scene Mechanics is twelve specific ways a scene stalls — it ends about where it started, nothing is really pushing it, you can call the beats before they land — with about forty finer versions underneath them. So when a scene drags, you find out what's dragging it — not just how much.
4/10 core
Several candidate threads compete and none governs — the scene splits its focus rather than committing to one determinate spine.
It isn’t clearly about one thing yet
7/10 core
A real force keeps it pushing forward
5/10 expected
The surface is full of events and motion, but the governing thread ends where it started — activity substitutes for evolution. Distinct from beats literally restating the same note.
It restates its note rather than deepening it
6/10 core
It turns — something is different by the end
7/10 expected
What happens here obliges what comes next
5/10 expected
The scene reaches its function and keeps going, or carries beats/lines cuttable without losing what it's there to do — waste not explained by the mechanism.
There’s avoidable waste on the page
5/10 expected
Page space and pacing emphasize the wrong beats — the important turn is rushed/buried while minor business is lingered on.
The parts sit side by side rather than building
7/10 core
The reader can follow what matters
4/10 light
It plays close to the version we’ve seen before
This scene's role doesn't owe this, so a low reading here is neutral rather than a fault.
5/10 light
The beats can be called before they land
This scene's role doesn't owe this, so a low reading here is neutral rather than a fault.
6/10 expected
The feeling comes off the page
7/10 core
The exit pulls you into the next one
This scene has been scored but its written read hasn’t been generated yet — the notes above are derived from the scores.
No explanation provided.
No explanation provided.
“Grab ‘em by the throat and never let ‘em go.”
The scene level score is the impact on the reader or audience to continue reading.
The Script score is how compelled they are to keep reading based on the rest of the script so far.
The scene ends with Namor captured, creating a strong cliffhanger about what will happen next, compelling the reader to continue.
Given the whole script, the capture of Namor is a major payoff, but the unresolved philosophical conflict and Shuri's vengeance arc keep the reader invested in the aftermath.
Design is broken — a load-bearing lens isn’t doing its job yet.
Craft Read is the familiar battery — concept, plot, characters, dialogue, stakes, pacing.
Scene Mechanics is twelve specific ways a scene stalls — it ends about where it started, nothing is really pushing it, you can call the beats before they land — with about forty finer versions underneath them. So when a scene drags, you find out what's dragging it — not just how much.
4/10 core
Several candidate threads compete and none governs — the scene splits its focus rather than committing to one determinate spine.
It isn’t clearly about one thing yet
5/10 core
It leans on mood instead of something actually pushing it
3/10 expected
The surface is full of events and motion, but the governing thread ends where it started — activity substitutes for evolution. Distinct from beats literally restating the same note.
It restates its note rather than deepening it
3/10 core
The unit connects, displays, or frames — it never attempts to change a dramatic condition. Distinct from a turn that is attempted but does not land (unclear_turn). An interlude doing its intended job is a craft choice, not this flaw.
It ends about where it started
5/10 expected
The result doesn’t oblige what comes next
3/10 expected
The scene reaches its function and keeps going, or carries beats/lines cuttable without losing what it's there to do — waste not explained by the mechanism.
There’s avoidable waste on the page
4/10 expected
Page space and pacing emphasize the wrong beats — the important turn is rushed/buried while minor business is lingered on.
The parts sit side by side rather than building
5/10 core
What matters is hard to follow
2/10 light
It plays close to the version we’ve seen before
This scene's role doesn't owe this, so a low reading here is neutral rather than a fault.
3/10 light
The beats can be called before they land
This scene's role doesn't owe this, so a low reading here is neutral rather than a fault.
4/10 expected
The emotion is described on the page rather than produced through the beats.
The feeling is stated more than felt
5/10 core
It settles at the exit rather than pulling on
This scene has been scored but its written read hasn’t been generated yet — the notes above are derived from the scores.
No explanation provided.
No explanation provided.
“Grab ‘em by the throat and never let ‘em go.”
The scene level score is the impact on the reader or audience to continue reading.
The Script score is how compelled they are to keep reading based on the rest of the script so far.
This scene compels forward with a cliffhanger: Namor is captured but the ship is damaged, and Shuri's plan is in motion. Readers want to see if the trap succeeds and how they escape the sinking ship.
Cumulatively, the script maintains strong momentum: unresolved vengeance arc, Talocan threat, Shuri's internal conflict, and the destruction of the Heart-Shaped Herb all push forward. This scene adds a raised stakes and a captured villain, which typically sustains reader investment.
All three lenses are solid — worth protecting as it stands.
HoldingA real force keeps it pushing forward.
Craft Read is the familiar battery — concept, plot, characters, dialogue, stakes, pacing.
Scene Mechanics is twelve specific ways a scene stalls — it ends about where it started, nothing is really pushing it, you can call the beats before they land — with about forty finer versions underneath them. So when a scene drags, you find out what's dragging it — not just how much.
7/10 core
It commits to one clear thing and holds it
8/10 core
A real force keeps it pushing forward
6/10 expected
The situation deepens as it goes
7/10 core
It turns — something is different by the end
7/10 expected
What happens here obliges what comes next
5/10 expected
The scene reaches its function and keeps going, or carries beats/lines cuttable without losing what it's there to do — waste not explained by the mechanism.
There’s avoidable waste on the page
6/10 expected
The parts are ordered and seamed so they build
7/10 core
The reader can follow what matters
4/10 light
It plays close to the version we’ve seen before
This scene's role doesn't owe this, so a low reading here is neutral rather than a fault.
5/10 light
The beats can be called before they land
This scene's role doesn't owe this, so a low reading here is neutral rather than a fault.
7/10 expected
The feeling comes off the page
8/10 core
The exit pulls you into the next one
This scene has been scored but its written read hasn’t been generated yet — the notes above are derived from the scores.
No explanation provided.
No explanation provided.
“Grab ‘em by the throat and never let ‘em go.”
The scene level score is the impact on the reader or audience to continue reading.
The Script score is how compelled they are to keep reading based on the rest of the script so far.
This scene compels continuation because the ship is still in danger and the Midnight Angels have just arrived, creating a cliffhanger. The reader wants to see if the rescue succeeds.
Given the whole script, the momentum is strong with the climactic battle and unresolved character arcs (Shuri's vengeance, Okoye's redemption). This scene maintains that momentum, though the technical focus slightly dampens emotional investment.
No lens is broken, but Design, Execution and Read are soft — this reads as a polish pass.
HoldingA real force keeps it pushing forward.
Craft Read is the familiar battery — concept, plot, characters, dialogue, stakes, pacing.
Scene Mechanics is twelve specific ways a scene stalls — it ends about where it started, nothing is really pushing it, you can call the beats before they land — with about forty finer versions underneath them. So when a scene drags, you find out what's dragging it — not just how much.
4/10 core
Several candidate threads compete and none governs — the scene splits its focus rather than committing to one determinate spine.
It isn’t clearly about one thing yet
6/10 core
A real force keeps it pushing forward
4/10 expected
The surface is full of events and motion, but the governing thread ends where it started — activity substitutes for evolution. Distinct from beats literally restating the same note.
It restates its note rather than deepening it
5/10 core
It ends about where it started
6/10 expected
What happens here obliges what comes next
4/10 expected
The scene reaches its function and keeps going, or carries beats/lines cuttable without losing what it's there to do — waste not explained by the mechanism.
There’s avoidable waste on the page
4/10 expected
Page space and pacing emphasize the wrong beats — the important turn is rushed/buried while minor business is lingered on.
The parts sit side by side rather than building
5/10 core
The reader can follow the events but can't tell what to weight — everything reads at equal importance, so the scene has no focal point.
What matters is hard to follow
3/10 expected
The scene's main situation/image/beat-pattern is recognizable genre convention and the script adds no specific inversion, collision, POV, cost, world-rule, or tonal twist that changes how it plays.
It plays close to the version we’ve seen before
3/10 expected
The scene sets up its conflict then plays the most likely version — no turn, reversal, complication, or reveal the reader couldn't call in advance.
The beats can be called before they land
5/10 core
The feeling is stated more than felt
6/10 core
The exit pulls you into the next one
This scene has been scored but its written read hasn’t been generated yet — the notes above are derived from the scores.
No explanation provided.
No explanation provided.
“Grab ‘em by the throat and never let ‘em go.”
The scene level score is the impact on the reader or audience to continue reading.
The Script score is how compelled they are to keep reading based on the rest of the script so far.
The scene ends with the duel unresolved and the ship battle ongoing, creating strong cliffhangers that compel the reader to continue.
The script maintains momentum through multiple concurrent threads (Shuri vs. Namor, ship battle, Midnight Angels), and the unresolved climax keeps the reader invested.
No lens is broken, but Design, Execution and Read are soft — this reads as a polish pass.
HoldingA real force keeps it pushing forward.
Craft Read is the familiar battery — concept, plot, characters, dialogue, stakes, pacing.
Scene Mechanics is twelve specific ways a scene stalls — it ends about where it started, nothing is really pushing it, you can call the beats before they land — with about forty finer versions underneath them. So when a scene drags, you find out what's dragging it — not just how much.
4/10 core
Several candidate threads compete and none governs — the scene splits its focus rather than committing to one determinate spine.
It isn’t clearly about one thing yet
6/10 core
A real force keeps it pushing forward
4/10 expected
Beats restate the same note; the reader’s experience does not change across the scene.
It restates its note rather than deepening it
5/10 core
It ends about where it started
6/10 expected
What happens here obliges what comes next
4/10 expected
The scene reaches its function and keeps going, or carries beats/lines cuttable without losing what it's there to do — waste not explained by the mechanism.
There’s avoidable waste on the page
4/10 expected
Page space and pacing emphasize the wrong beats — the important turn is rushed/buried while minor business is lingered on.
The parts sit side by side rather than building
6/10 core
The reader can follow what matters
3/10 light
It plays close to the version we’ve seen before
This scene's role doesn't owe this, so a low reading here is neutral rather than a fault.
4/10 light
The beats can be called before they land
This scene's role doesn't owe this, so a low reading here is neutral rather than a fault.
5/10 expected
The feeling is stated more than felt
6/10 core
The exit pulls you into the next one
This scene has been scored but its written read hasn’t been generated yet — the notes above are derived from the scores.
No explanation provided.
No explanation provided.
“Grab ‘em by the throat and never let ‘em go.”
The scene level score is the impact on the reader or audience to continue reading.
The Script score is how compelled they are to keep reading based on the rest of the script so far.
The scene ends with Shuri pursuing Namor and Okoye showing mercy, leaving open questions about the final outcome and the Talocanil threat, compelling the reader to continue.
Given the whole script, the accumulated momentum of Shuri's journey and the unresolved war with Talocanil strongly pull the reader forward, though the intercutting slightly dampens the drive.
All three lenses are solid — worth protecting as it stands.
HoldingIt turns — something is different by the end.
Craft Read is the familiar battery — concept, plot, characters, dialogue, stakes, pacing.
Scene Mechanics is twelve specific ways a scene stalls — it ends about where it started, nothing is really pushing it, you can call the beats before they land — with about forty finer versions underneath them. So when a scene drags, you find out what's dragging it — not just how much.
7/10 core
It commits to one clear thing and holds it
6/10 core
A real force keeps it pushing forward
5/10 expected
Beats restate the same note; the reader’s experience does not change across the scene.
It restates its note rather than deepening it
8/10 core
It turns — something is different by the end
7/10 core
What happens here obliges what comes next
6/10 expected
Every beat and line earns its place
6/10 expected
The parts are ordered and seamed so they build
8/10 core
The reader can follow what matters
5/10 light
It plays close to the version we’ve seen before
This scene's role doesn't owe this, so a low reading here is neutral rather than a fault.
4/10 light
The beats can be called before they land
This scene's role doesn't owe this, so a low reading here is neutral rather than a fault.
7/10 core
The feeling comes off the page
7/10 core
The exit pulls you into the next one
This scene has been scored but its written read hasn’t been generated yet — the notes above are derived from the scores.
No explanation provided.
No explanation provided.
“Grab ‘em by the throat and never let ‘em go.”
The scene level score is the impact on the reader or audience to continue reading.
The Script score is how compelled they are to keep reading based on the rest of the script so far.
The scene resolves the central conflict, so there is no cliffhanger—but the final threat ('I will find and kill you') creates a lingering tension that makes the reader curious about the aftermath and the new alliance.
Given the whole script, the reader is pulled forward by the need to see the aftermath of the alliance, the fate of the characters (especially Ross and Val), and whether Shuri's choice will hold. The momentum is strong but slightly diminished by the clean resolution.
All three lenses are solid — worth protecting as it stands.
HoldingWhat happens here obliges what comes next.
Craft Read is the familiar battery — concept, plot, characters, dialogue, stakes, pacing.
Scene Mechanics is twelve specific ways a scene stalls — it ends about where it started, nothing is really pushing it, you can call the beats before they land — with about forty finer versions underneath them. So when a scene drags, you find out what's dragging it — not just how much.
7/10 core
It commits to one clear thing and holds it
7/10 core
A real force keeps it pushing forward
6/10 expected
The situation deepens as it goes
7/10 core
It turns — something is different by the end
8/10 core
What happens here obliges what comes next
6/10 expected
Every beat and line earns its place
6/10 expected
The parts are ordered and seamed so they build
8/10 core
The reader can follow what matters
5/10 light
It plays close to the version we’ve seen before
This scene's role doesn't owe this, so a low reading here is neutral rather than a fault.
6/10 light
It defeats anticipation fairly
This scene's role doesn't owe this, so a low reading here is neutral rather than a fault.
7/10 core
The feeling comes off the page
8/10 core
The exit pulls you into the next one
This scene has been scored but its written read hasn’t been generated yet — the notes above are derived from the scores.
No explanation provided.
No explanation provided.
“Grab ‘em by the throat and never let ‘em go.”
The scene level score is the impact on the reader or audience to continue reading.
The Script score is how compelled they are to keep reading based on the rest of the script so far.
The scene ends with Ross being arrested and sirens approaching, creating a strong cliffhanger that makes the reader want to see what happens next.
Given the whole script, this scene adds a new mystery (blue-skinned attackers) and raises the stakes for Ross, maintaining momentum from the previous political and action threads.
Design is broken — a load-bearing lens isn’t doing its job yet.
HoldingEvery beat and line earns its place.
Craft Read is the familiar battery — concept, plot, characters, dialogue, stakes, pacing.
Scene Mechanics is twelve specific ways a scene stalls — it ends about where it started, nothing is really pushing it, you can call the beats before they land — with about forty finer versions underneath them. So when a scene drags, you find out what's dragging it — not just how much.
4/10 core
For most of the scene the POV observes activity with no visible intention, scene question, threat, pursuit, or decision organizing what the reader is meant to track.
It isn’t clearly about one thing yet
5/10 core
It leans on mood instead of something actually pushing it
2/10 expected
The surface is full of events and motion, but the governing thread ends where it started — activity substitutes for evolution. Distinct from beats literally restating the same note.
It restates its note rather than deepening it
3/10 core
The unit connects, displays, or frames — it never attempts to change a dramatic condition. Distinct from a turn that is attempted but does not land (unclear_turn). An interlude doing its intended job is a craft choice, not this flaw.
It ends about where it started
5/10 expected
The result doesn’t oblige what comes next
6/10 expected
Every beat and line earns its place
5/10 expected
The parts sit side by side rather than building
6/10 core
The reader can follow what matters
3/10 light
The scene's main situation/image/beat-pattern is recognizable genre convention and the script adds no specific inversion, collision, POV, cost, world-rule, or tonal twist that changes how it plays.
It plays close to the version we’ve seen before
This scene's role doesn't owe this, so a low reading here is neutral rather than a fault.
3/10 light
The scene sets up its conflict then plays the most likely version — no turn, reversal, complication, or reveal the reader couldn't call in advance.
The beats can be called before they land
This scene's role doesn't owe this, so a low reading here is neutral rather than a fault.
4/10 expected
The emotion is described on the page rather than produced through the beats.
The feeling is stated more than felt
5/10 core
It settles at the exit rather than pulling on
This scene has been scored but its written read hasn’t been generated yet — the notes above are derived from the scores.
No explanation provided.
No explanation provided.
“Grab ‘em by the throat and never let ‘em go.”
The scene level score is the impact on the reader or audience to continue reading.
The Script score is how compelled they are to keep reading based on the rest of the script so far.
The scene ends with a clear hook: Okoye says 'Let's go,' and then cuts to Namor's cave, creating curiosity about what happens next with both Ross and Namor.
Given the whole script, the rescue of Ross is a minor but welcome beat, and the cut to Namor's cave maintains momentum from the previous battle. The story still has threads about Talocan and Wakanda's future, keeping interest high.
No lens is broken, but Design and Read are soft — this reads as a polish pass.
An aftermath beat lands the cost of what just happened rather than driving new action.
HoldingThe reader can follow what matters.
Craft Read is the familiar battery — concept, plot, characters, dialogue, stakes, pacing.
Scene Mechanics is twelve specific ways a scene stalls — it ends about where it started, nothing is really pushing it, you can call the beats before they land — with about forty finer versions underneath them. So when a scene drags, you find out what's dragging it — not just how much.
6/10 core
It commits to one clear thing and holds it
4/10 expected
The scene asserts tension/stakes/unease but no locatable page-visible force produces it — mood is mistaken for pressure (the pressure firewall).
It leans on mood instead of something actually pushing it
5/10 expected
It restates its note rather than deepening it
5/10 core
It ends about where it started
6/10 core
What happens here obliges what comes next
6/10 expected
Every beat and line earns its place
5/10 expected
The scene/sequence shifts location, time, POV, mode, or thread without making the causal/spatial/emotional/rhythmic relationship between adjacent chunks legible.
The parts sit side by side rather than building
7/10 core
The reader can follow what matters
4/10 light
It plays close to the version we’ve seen before
This scene's role doesn't owe this, so a low reading here is neutral rather than a fault.
4/10 light
The beats can be called before they land
This scene's role doesn't owe this, so a low reading here is neutral rather than a fault.
5/10 expected
The emotion is described on the page rather than produced through the beats.
The feeling is stated more than felt
5/10 core
The unit completes its business and ends on a settled beat — no new live question, demand, or expectation is created for the next unit to inherit.
It settles at the exit rather than pulling on
This scene has been scored but its written read hasn’t been generated yet — the notes above are derived from the scores.
No explanation provided.
No explanation provided.
“Grab ‘em by the throat and never let ‘em go.”
The scene level score is the impact on the reader or audience to continue reading.
The Script score is how compelled they are to keep reading based on the rest of the script so far.
This scene feels self-contained and does not create a strong hook for the next scene, as it resolves most threads and ends on a peaceful note.
Given the whole script, the reader is likely satisfied with the resolution but may be curious about Ross's fate and Val's machinations, which were set up earlier; this scene loses some momentum.
No lens is broken, but Design and Read are soft — this reads as a polish pass.
A ritual beat repeats a known pattern on purpose, so movement and freshness read low by design.
HoldingThe reader can follow what matters.
Craft Read is the familiar battery — concept, plot, characters, dialogue, stakes, pacing.
Scene Mechanics is twelve specific ways a scene stalls — it ends about where it started, nothing is really pushing it, you can call the beats before they land — with about forty finer versions underneath them. So when a scene drags, you find out what's dragging it — not just how much.
6/10 core
It commits to one clear thing and holds it
4/10 core
The scene asserts tension/stakes/unease but no locatable page-visible force produces it — mood is mistaken for pressure (the pressure firewall).
It leans on mood instead of something actually pushing it
4/10 expected
Beats restate the same note; the reader’s experience does not change across the scene.
It restates its note rather than deepening it
5/10 core
The unit connects, displays, or frames — it never attempts to change a dramatic condition. Distinct from a turn that is attempted but does not land (unclear_turn). An interlude doing its intended job is a craft choice, not this flaw.
It ends about where it started
6/10 expected
What happens here obliges what comes next
7/10 expected
Every beat and line earns its place
6/10 expected
The parts are ordered and seamed so they build
8/10 core
The reader can follow what matters
3/10 light
The scene's main situation/image/beat-pattern is recognizable genre convention and the script adds no specific inversion, collision, POV, cost, world-rule, or tonal twist that changes how it plays.
It plays close to the version we’ve seen before
This scene's role doesn't owe this, so a low reading here is neutral rather than a fault.
4/10 light
The scene sets up its conflict then plays the most likely version — no turn, reversal, complication, or reveal the reader couldn't call in advance.
The beats can be called before they land
This scene's role doesn't owe this, so a low reading here is neutral rather than a fault.
5/10 expected
The emotion is described on the page rather than produced through the beats.
The feeling is stated more than felt
6/10 core
The exit pulls you into the next one
This scene has been scored but its written read hasn’t been generated yet — the notes above are derived from the scores.
No explanation provided.
No explanation provided.
“Grab ‘em by the throat and never let ‘em go.”
The scene level score is the impact on the reader or audience to continue reading.
The Script score is how compelled they are to keep reading based on the rest of the script so far.
The scene feels self-contained and doesn't create a strong cliffhanger, but it sets up M'Baku's new role, making the reader curious about how he'll lead.
Given the script's momentum from the previous action-heavy scenes, this quieter moment provides a breather but may slow engagement; the unresolved threads with Namor and Shuri's emotional state still pull the reader forward.
All three lenses are solid — worth protecting as it stands.
HoldingIt turns — something is different by the end.
Craft Read is the familiar battery — concept, plot, characters, dialogue, stakes, pacing.
Scene Mechanics is twelve specific ways a scene stalls — it ends about where it started, nothing is really pushing it, you can call the beats before they land — with about forty finer versions underneath them. So when a scene drags, you find out what's dragging it — not just how much.
7/10 core
It commits to one clear thing and holds it
4/10 expected
The scene asserts tension/stakes/unease but no locatable page-visible force produces it — mood is mistaken for pressure (the pressure firewall).
It leans on mood instead of something actually pushing it
6/10 expected
The situation deepens as it goes
8/10 core
It turns — something is different by the end
7/10 core
What happens here obliges what comes next
6/10 expected
Every beat and line earns its place
7/10 expected
The parts are ordered and seamed so they build
8/10 core
The reader can follow what matters
5/10 light
It plays close to the version we’ve seen before
This scene's role doesn't owe this, so a low reading here is neutral rather than a fault.
6/10 light
It defeats anticipation fairly
This scene's role doesn't owe this, so a low reading here is neutral rather than a fault.
7/10 core
The feeling comes off the page
8/10 core
The exit pulls you into the next one
This scene has been scored but its written read hasn’t been generated yet — the notes above are derived from the scores.
No explanation provided.
No explanation provided.
“Grab ‘em by the throat and never let ‘em go.”
The scene level score is the impact on the reader or audience to continue reading.
The Script score is how compelled they are to keep reading based on the rest of the script so far.
The scene ends on a hopeful, open note, making the reader curious about Toussaint's future and Shuri's new role as aunt. It compels continuation.
The script has built strong momentum through action and political conflict, and this emotional denouement provides a satisfying payoff while opening new threads (Toussaint's destiny, Okoye's journey). The reader is invested in seeing how these threads develop.
No lens is broken, but Design and Read are soft — this reads as a polish pass.
HoldingEvery beat and line earns its place.
Craft Read is the familiar battery — concept, plot, characters, dialogue, stakes, pacing.
Scene Mechanics is twelve specific ways a scene stalls — it ends about where it started, nothing is really pushing it, you can call the beats before they land — with about forty finer versions underneath them. So when a scene drags, you find out what's dragging it — not just how much.
7/10 core
It commits to one clear thing and holds it
4/10 expected
The scene asserts tension/stakes/unease but no locatable page-visible force produces it — mood is mistaken for pressure (the pressure firewall).
It leans on mood instead of something actually pushing it
4/10 expected
Beats restate the same note; the reader’s experience does not change across the scene.
It restates its note rather than deepening it
6/10 core
It turns — something is different by the end
5/10 expected
The scene delivers information or understanding but no one is forced to decide or act on it.
The result doesn’t oblige what comes next
8/10 core
Every beat and line earns its place
7/10 expected
The parts are ordered and seamed so they build
8/10 core
The reader can follow what matters
5/10 light
It plays close to the version we’ve seen before
This scene's role doesn't owe this, so a low reading here is neutral rather than a fault.
4/10 light
The beats can be called before they land
This scene's role doesn't owe this, so a low reading here is neutral rather than a fault.
8/10 core
The feeling comes off the page
6/10 core
The unit completes its business and ends on a settled beat — no new live question, demand, or expectation is created for the next unit to inherit.
The exit pulls you into the next one
This scene has been scored but its written read hasn’t been generated yet — the notes above are derived from the scores.
No explanation provided.
No explanation provided.
“Grab ‘em by the throat and never let ‘em go.”
The scene level score is the impact on the reader or audience to continue reading.
The Script score is how compelled they are to keep reading based on the rest of the script so far.
This scene provides a strong emotional closure, making it feel like a natural ending point. However, the introduction of Toussaint creates curiosity about his future role, compelling the reader to continue to see how this new character will be integrated.
Given the entire script, this scene is the emotional climax of Shuri's arc and the thematic resolution. The reader is pulled to continue because the film is ending, and this scene provides a satisfying conclusion while hinting at future stories.
The screenplay effectively utilizes character development to drive the narrative and create emotional engagement. Characters undergo significant transformations, and their motivations and conflicts are well-explored. However, there is room for refinement in enhancing character complexity and ensuring consistent character growth throughout the story.
The screenplay demonstrates a strong foundation in character development, presenting characters with depth, complexity, and transformative arcs. The relationships between characters are well-established, and their interactions drive the narrative forward. However, some characters could benefit from further development to enhance their relatability and emotional impact on the audience.
The screenplay presents a compelling premise that sets up an intriguing conflict between Wakanda and Talocan, driven by the characters' motivations and the search for vibranium. However, it could benefit from further refining the narrative to enhance its clarity and audience engagement, particularly in the execution and depth of the conflict resolution.
The screenplay's premise introduces a compelling conflict between the advanced African nation of Wakanda and the underwater kingdom of Talocan, each seeking control over the precious resource, vibranium. The inclusion of a hidden underwater civilization adds a unique element to the story, and the potential for political intrigue and cultural clashes adds depth to the thematic exploration. The introduction of new characters, such as Riri Williams and Namora, brings diverse perspectives and motivations into the mix. Overall, the premise is intriguing and has the potential to captivate the audience.
The screenplay exhibits a sturdy narrative structure and effectively balances its multiple plotlines, showcasing the clash between Wakanda and Talocan, while exploring themes of grief, legacy, and the responsibility of leadership. The screenplay deftly handles the task of balancing character arcs with the advancement of the central conflict, resulting in a compelling and engaging storyline. While the pacing remains steady throughout, there are moments where the plot could benefit from refinement to elevate the tension and emotional impact.
The screenplay's structure adheres to the traditional three-act structure, providing a clear and coherent framework for the story to unfold. The introduction establishes the central conflict and introduces the main characters, setting the stage for the ensuing events. The rising action builds tension through the escalating conflict between Wakanda and Talocan, while the falling action brings the conflict to a head, leading to a resolution that ties up the plot threads and provides closure to the character arcs. The screenplay effectively juggles multiple subplots involving the characters' personal struggles, adding depth and emotional resonance to the overarching narrative.
The screenplay adeptly explores themes of identity, legacy, and the clash between tradition and progress through its well-developed characters and engaging narrative. While some areas could be refined to enhance thematic depth, the screenplay holds promise for delivering a thought-provoking and emotionally resonant experience.
The screenplay's exploration of themes and messages is commendable. It delves into the themes of identity, legacy, and the clash between tradition and progress, which are skillfully interwoven into the narrative. The character arcs and relationships serve as vehicles for exploring these themes, providing depth and emotional resonance. However, certain aspects could be strengthened to further elevate the screenplay's thematic impact.
"Black Panther: Wakanda Forever" presents a richly imagined and visually captivating cinematic experience. The screenplay's imagery is characterized by its vivid and evocative descriptions of the vibrant Afro-futuristic world of Wakanda and its captivating underwater counterpart, Talocan.
The visual imagery employed in "Black Panther: Wakanda Forever" effectively captures the essence of the narrative, with scenes that are both visually striking and emotionally evocative. The vibrant colors, intricate costumes, and stunning landscapes create a world that feels both immersive and unique. Furthermore, the balance between traditional African aesthetics and modern technology results in a visually distinctive and memorable experience. While the film successfully maintains its visual style throughout, there are opportunities to enhance the creativity and dynamism of certain scenes, which could further elevate the visual storytelling.
The screenplay elicits a range of emotions, with its strengths lying in the depth of emotional responses it evokes. However, there are opportunities to enhance the emotional depth and resonance by delving deeper into the characters' internal conflicts and exploring their motivations and backstories.
The screenplay effectively utilizes the characters' personal journeys and the clash between Wakanda and Talocan to generate emotional responses. The themes of grief, vengeance, and the struggle for self-determination resonate with the audience, creating a compelling and emotionally engaging narrative. However, the focus on spectacle and action sequences sometimes overshadows the emotional development of the characters, and the resolution of some conflicts feels abrupt.
The screenplay effectively presents conflict and stakes, although there are areas where they could be further enhanced to deepen tension and elevate audience engagement. The central conflict between Wakanda and Talocan is clear and compelling, with personal stakes that drive the characters' actions and decisions. However, some subplots lack the same level of significance and integration, potentially diluting the overall impact of the conflict.
The screenplay's conflict and stakes are generally well-crafted, providing a solid foundation for narrative tension and audience engagement. The central conflict between Wakanda and Talocan is compelling, with high stakes that directly impact the characters' lives, motivations, and relationships. However, some subplots, such as the romantic entanglement between Okoye and Aneka, feel less significant and integrated into the main narrative. Additionally, while the stakes are often personal, they could be further elevated by exploring their wider implications and consequences.
The screenplay displays an impressive level of originality and creativity in its blend of Afro-futuristic elements with a superhero narrative. The film's focus on Wakanda's distinct culture, its seamless integration of mythology, technology, and action sequences sets it apart from typical superhero films.
The screenplay for Black Panther: Wakanda Forever exhibits notable originality and creativity in its storytelling, characters, and thematic exploration. It successfully expands on the world-building of its predecessor while introducing compelling new characters and storylines.
Thank you for your feedback!
Get a comprehensive PDF version of your screenplay analysis
The PDF version is a static summary of your analysis. Due to format and interactivity constraints, the PDF does not include all the data available in the web version.
What's not in the PDF: Interactive charts, expandable sections, full scene-by-scene details, AI chat history, and dynamic filtering options are not available in the PDF format. For the complete analysis experience, use the web interface.
Click below to generate and download your PDF analysis summary
Download PDFPDF generation may take 20-30 seconds
Tip: For sharing purposes, consider using the web link instead. It provides real-time access to all features and updates automatically.
Scene by Scene Emotions