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. Other loglines ›
How to read these: in industry coverage, Pass is the default outcome for the majority of professional scripts, and Consider means the reader stayed in the room. Industry-wide, the median professional evaluation sits at a 6 — scores of 8+ are rare everywhere, on purpose.
A mainstream franchise sequel with a distinctive emotional core and vivid cultural world-building that requires targeted structural tightening in the middle act before it can be championed.
A mainstream commercial superhero epic aiming to combine large-scale action and franchise worldbuilding with an emotionally grounded story about grief, cultural memory, and choosing protection over vengeance.
The script’s strong opening, distinctive cultural world-building, and coherent emotional core provide enough assets to sustain a Consider call despite structural strain.
The middle-act fragmentation and the under-dramatized climax require targeted structural revision before the script can consistently read as a Recommend.
A script with a distinctive emotional core and vivid cultural world-building that needs targeted structural work on middle-act focus and the climax’s emotional payoff.
Read as Mainstream commercial / Elevated commercial
Anchoring each middle sequence to a concrete shift in Shuri’s objective or emotional state addresses both the fragmented throughline and the antagonist’s pivot, restoring causal pressure without sacrificing the cultural world-building.
The script consistently grounds Shuri’s loss in physical rituals and family memory, giving the blockbuster spectacle a human core that distinguishes it from standard genre fare.
Compressing the middle act to restore momentum risks reducing the Talocan sequences to exposition or military threat, stripping away the cultural grounding that makes the conflict morally legible.
When tightening the second act, preserve the ordinary life, ritual, and bioluminescent detail of the underwater city as self-contained beats rather than trimming them to serve plot mechanics.
The reader loses forward pull as the script cuts between multiple storylines and worldbuilding sequences without a single accumulating objective for the protagonist.
The draft balances grief, political intrigue, and the Talocan introduction as separate modules rather than weaving them into a shared causal chain, leaving Shuri’s emotional journey reactive instead of driven.
One path is to anchor each middle sequence to a concrete shift in Shuri’s immediate objective or emotional state, so the Talocan visit, the scientist hunt, and the political fallout form a single escalating chain rather than adjacent episodes.
The reader struggles to anchor Namor’s threat and feels the final mercy turn arrives as a thematic statement rather than an earned choice, which flattens the emotional payoff of the climax.
Namor’s demands shift from alliance to war without a dramatized decision point, and Shuri’s choice to spare him bypasses a visible internal reckoning, making the resolution feel convenient.
One path is to insert a clear cost or decision beat for Namor before the war declaration, and to let Shuri’s restraint emerge through a specific action during the confrontation before the final offer.
Remove visible alternate dialogue lines, placeholder notes, and recurring typos, and replace caps-heavy action beats with clean, descriptive prose that trusts the staging to carry intensity.
The script’s distinctive emotional and cultural core, anchored in grief, ritual, and the Talocan world-building, provides a clear advocacy anchor.
The diffusion of focus across parallel storylines and worldbuilding in the middle act dilutes the protagonist’s emotional journey, making it the primary obstacle to a stronger advocacy call.
On the score: The score sits at the high edge of its band — a focused revision could push it to the next verdict.
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.
Your whole script read on three things — Design (is it built), Execution (does it play on the page), and Involvement (does it draw you in) — then mapped scene by scene. The rows go Script → Acts → Sequences → Scenes in story order, left to right; a unit’s width is its length in pages.
Colour depends on the mode. By default you’re on Triage — a recommendation for each part: Keep (green), Polish, Rework, or Two groups low (red). Switch Colour by (top) to a group (Design / Execution / Involvement) or one of the twelve axes and the colour becomes that signal’s score instead — red (needs work) through green (strong), with grey where a part isn’t owed that signal. Either way it’s a map of where to look.
To explore: click any cell for its detailed read — what’s working, what’s dragging, and your options — and 💬 Ask about it right there. To see an act’s scenes larger, hover the act and click Zoom in (the magnifier); Zoom out in the same spot, or Esc, goes back. While zoomed, the other acts stay as narrow strips you can click, and ← → move between them. Use Colour by (top) to recolour by a single craft signal, or the Findings / Axes / Patterns tabs to read it different ways.
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 delivers a deeply emotional and thematically rich character journey, anchored by Shuri's transformation from a grief-stricken princess into a vengeful yet ultimately merciful Black Panther. Namor is a standout antagonist, given a tragic backstory that makes his threat feel justified and his eventual alliance earned. Supporting characters like Okoye and Nakia receive meaningful arcs, though several secondary figures—particularly M'Baku, Namora, and the tribal elders—remain underdeveloped. The script's greatest strength is its willingness to let grief drive character decisions, creating a resonant and human core beneath the superhero spectacle.
Analysis: The screenplay establishes a genuinely moving and culturally specific premise—a grieving Wakanda confronted by an underwater Mayan superpower—and uses it to power a resonant coming-of-rage arc for Shuri. The foundational idea is clear and emotionally engaging, but the premise is somewhat weakened by a slow geopolitical front-load, a familiar hidden-kingdom antagonist structure, and an overstuffed middle act that delays the central confrontation.
Analysis: The screenplay possesses a strong emotional core, anchored by Shuri's grief-driven arc, a devastating midpoint turn, and a thematically resonant finale. The structure, however, sags in the middle—particularly in the extended Boston chase and the Talocan interludes—and struggles to fully clarify Namor's shifting motivations. The Wakanda attack and Killmonger Ancestral Plane sequence are standout dramatic moments. Overall, the narrative is ambitious and emotionally effective, but pacing and plot coherence in the second act would benefit from tightening.
Analysis: The screenplay effectively centers its thematic exploration around grief, vengeance versus mercy, and the legacy of loss, achieving an emotionally coherent and strong narrative arc. It successfully connects Shuri's personal transformation to larger themes of leadership, nationhood, and breaking cycles of violence, though it sometimes states its themes explicitly rather than letting them emerge organically. The bold choice to have Shuri spare Namor and the final reveal of T'Challa's son provide emotional and thematic closure, deepening the resonance of the story. However, the thematic treatment could be more novel in spots, and the role of tradition versus innovation deserves a sharper resolution.
Analysis: Black Panther: Wakanda Forever's screenplay presents a visually ambitious and emotionally grounded sequel that uses spectacle in service of grief. The imagery is strongest when it fuses personal ritual with mythic scale—the levitating funeral casket, the bioluminescent Talocan, the flooded throne room—and weakest in generic action shorthand and conventional government-thriller backdrops. The visual language of water, fire, and mourning clothes is deployed with sophistication, creating a rich foundation for a director and production designer to build upon.
Analysis: The screenplay delivers a powerful emotional journey centered on grief, legacy, and the burden of leadership. Shuri's arc from rage to reluctant mercy is the emotional backbone, supported by culturally rich mourning rituals and a cathartic final reveal. However, some emotional beats—particularly Ramonda's death, Okoye's dismissal, and Riri's integration—are underdeveloped or rushed, preventing the story from achieving its full resonant potential.
Analysis: The screenplay establishes a clear and emotionally charged central conflict between Wakanda and Namor, anchored by Shuri's grief and evolution. The stakes are high—national survival, personal vengeance, and the fate of two hidden civilizations—but several supporting threads, particularly the U.S. political subplot and Shuri's final psychological turn, are underdeveloped. Strong action and character-driven tension make the narrative engaging, though causal connections and the cost of resolution could be tightened.
Analysis: This screenplay delivers a culturally rich and emotionally grounded sequel that expands the Wakandan mythos into an underwater Mesoamerican civilization. Its greatest creative assets are the vivid world-building of Talocan, the subversion of Shuri's ancestral-plane confrontation, and a final reveal that re-centers the story on legacy and hope. While the broad three-act structure hews to familiar superhero conventions, the script consistently freshens familiar tropes with cultural specificity, thematic weight, and character-driven choices.
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 Involvement 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 Involvement 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 Involvement 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 Involvement 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 Involvement 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 Involvement 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 Involvement 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 Involvement 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 Involvement 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 Involvement 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 Involvement 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 Involvement are broken — this reads as a rebuild before polish.
It ends about where it started Movement
HoldingThe reader can follow what matters.
Involvement 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 Involvement 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 Involvement 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 Involvement 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.
Involvement 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 Involvement 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 Involvement 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 Involvement 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 Involvement 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 Involvement 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.
Involvement 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 Involvement 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 Involvement 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 Involvement 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 Involvement 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 Involvement 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 Involvement 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 Involvement 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 Involvement 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 Involvement 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 Involvement 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 Involvement 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 Involvement 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 | 8 / 9 | 8 / 8 | 7 | 7 | 6 | 7 | 6 | 7 | 8 | 7 | 6 | 8 | 8 | 5 | 8 | 7 | 7 | 8 | 9 | 8 | |
| 2 - T'Challa's Funeral | PolishRitualNo lens is broken, but Design, Execution and Involvement are soft — this reads as a polish pass. | SoftThe structure works but is leaking power in places. | 6 | 7 / 7 | 6 / 6 | 7 | 5 | 6 | 6 | 5 | 5 | 4 | 4 | 3 | 5 | 5 | 4 | 7 | 5 | 6 | 6 | 7 | 6 | |
| 3 - UN Ambush | KeepContestAll three lenses are solid — worth protecting as it stands. | SolidThe story machine is built and mostly working. | 6 | 8 / 8 | 7 / 7 | 6 | 6 | 5 | 7 | 5 | 5 | 7 | 7 | 6 | 7 | 6 | 5 | 5 | 7 | 6 | 6 | 8 | 7 | |
| 4 - Hostage Crisis and Diplomatic Tensions | KeepPursuitAll three lenses are solid — worth protecting as it stands. | SolidThe story machine is built and mostly working. | 7 | 8 / 8 | 7 / 7 | 7 | 7 | 6 | 7 | 5 | 4 | 8 | 7 | 6 | 7 | 8 | 6 | 5 | 6 | 7 | 7 | 8 | 7 | |
| 5 - Deep-Sea Disaster | PolishInvestigationNo lens is broken, but Design, Execution and Involvement are soft — this reads as a polish pass. | SoftThe structure works but is leaking power in places. | 7 | 8 / 8 | 8 / 7 | 7 | 7 | 6 | 5 | 4 | 3 | 7 | 7 | 6 | 7 | 8 | 7 | 6 | 6 | 7 | 7 | 8 | 7 | |
| 6 - Talocanil Invasion at Sea | KeepPursuitAll three lenses are solid — worth protecting as it stands. | SolidThe story machine is built and mostly working. | 7 | 8 / 7 | 8 / 7 | 7 | 7 | 7 | 6 | 5 | 4 | 7 | 7 | 7 | 6 | 8 | 7 | 5 | 6 | 7 | 8 | 8 | 7 | |
| 7 - Attacks and Explosions | PolishAftermathNo lens is broken, but Design, Execution and Involvement are soft — this reads as a polish pass. | SoftThe structure works but is leaking power in places. | 6 | 8 / 7 | 7 / 7 | 6 | 6 | 5 | 5 | 4 | 3 | 6 | 7 | 6 | 7 | 7 | 6 | 5 | 6 | 7 | 7 | 8 | 7 | |
| 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 | 8 / 8 | 6 / 6 | 7 | 6 | 5 | 7 | 6 | 7 | 5 | 6 | 6 | 6 | 6 | 5 | 7 | 7 | 6 | 6 | 8 | 6 | |
| 9 - Grief and Rituals | KeepRitualAll three lenses are solid — worth protecting as it stands. | SolidThe story machine is built and mostly working. | 7 | 8 / 8 | 7 / 7 | 7 | 6 | 6 | 8 | 7 | 7 | 5 | 7 | 7 | 7 | 6 | 6 | 8 | 8 | 7 | 6 | 8 | 7 | |
| 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. | 7 | 8 / 8 | 8 / 8 | 7 | 7 | 7 | 7 | 6 | 5 | 8 | 7 | 8 | 8 | 8 | 7 | 6 | 7 | 8 | 7 | 8 | 7 | |
| 11 - Tribal Council Meeting | PolishDeliberationNo lens is broken, but Design and Involvement are soft — this reads as a polish pass. | SoftThe structure works but is leaking power in places. | 6 | 8 / 7 | 5 / 6 | 6 | 6 | 5 | 7 | 5 | 4 | 7 | 6 | 5 | 6 | 6 | 4 | 4 | 6 | 5 | 5 | 8 | 6 | |
| 12 - The Vibranium Detector | PolishInvestigationNo lens is broken, but Design and Involvement are soft — this reads as a polish pass. | SoftThe structure works but is leaking power in places. | 7 | 7 / 6 | 5 / 6 | 7 | 7 | 6 | 7 | 6 | 5 | 8 | 5 | 4 | 5 | 8 | 4 | 4 | 6 | 5 | 6 | 8 | 6 | |
| 13 - Finding the Scientist | KeepDeliveryAll three lenses are solid — worth protecting as it stands. | SolidThe story machine is built and mostly working. | 7 | 8 / 7 | 6 / 7 | 7 | 7 | 7 | 8 | 6 | 5 | 8 | 6 | 5 | 6 | 8 | 5 | 5 | 7 | 6 | 6 | 8 | 6 | |
| 14 - Riri's Garage Raid | KeepPursuitAll three lenses are solid — worth protecting as it stands. | SolidThe story machine is built and mostly working. | 7 | 8 / 8 | 8 / 8 | 6 | 7 | 5 | 7 | 6 | 5 | 8 | 7 | 6 | 7 | 8 | 6 | 5 | 7 | 7 | 7 | 6 | 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 | 8 / 8 | 8 / 8 | 6 | 6 | 5 | 7 | 5 | 4 | 8 | 7 | 6 | 7 | 7 | 6 | 5 | 7 | 7 | 7 | 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 | 7 / 8 | 8 / 7 | 6 | 6 | 5 | 7 | 5 | 4 | 7 | 7 | 6 | 7 | 6 | 6 | 5 | 7 | 7 | 8 | 8 | 7 | |
| 17 - Escape from Cambridge | PolishPursuitNo lens is broken, but Design, Execution and Involvement are soft — this reads as a polish pass. | SoftThe structure works but is leaking power in places. | 6 | 7 / 8 | 8 / 7 | 6 | 6 | 5 | 6 | 5 | 4 | 7 | 7 | 6 | 7 | 6 | 6 | 5 | 6 | 7 | 8 | 8 | 7 | |
| 18 - High-Flying Rescue | PolishPursuitNo lens is broken, but Design, Execution and Involvement are soft — this reads as a polish pass. | SoftThe structure works but is leaking power in places. | 6 | 8 / 8 | 6 / 7 | 6 | 7 | 5 | 6 | 5 | 4 | 8 | 6 | 5 | 6 | 7 | 5 | 4 | 5 | 6 | 7 | 7 | 6 | |
| 19 - Bridge Battle | KeepPursuitAll three lenses are solid — worth protecting as it stands. | SolidThe story machine is built and mostly working. | 7 | 7 / 8 | 8 / 8 | 7 | 7 | 6 | 7 | 6 | 5 | 8 | 8 | 7 | 8 | 8 | 7 | 6 | 6 | 8 | 7 | 6 | 7 | |
| 20 - Escape from Cambridge | PolishInvestigationNo lens is broken, but Design and Involvement are soft — this reads as a polish pass. | SoftThe structure works but is leaking power in places. | 6 | 8 / 7 | 7 / 7 | 6 | 7 | 5 | 7 | 6 | 5 | 7 | 6 | 5 | 7 | 8 | 6 | 5 | 6 | 6 | 6 | 8 | 7 | |
| 21 - Okoye Loses Everything | KeepAftermathAll three lenses are solid — worth protecting as it stands. | SolidThe story machine is built and mostly working. | 7 | 9 / 9 | 8 / 8 | 7 | 7 | 6 | 8 | 7 | 6 | 8 | 8 | 7 | 8 | 8 | 6 | 9 | 8 | 8 | 8 | 9 | 8 | |
| 22 - In Pursuit of Wakandans | PolishTransitionNo lens is broken, but Design and Involvement are soft — this reads as a polish pass. | SoftThe structure works but is leaking power in places. | 6 | 7 / 7 | 5 / 6 | 6 | 6 | 5 | 6 | 5 | 5 | 7 | 6 | 5 | 6 | 7 | 5 | 4 | 6 | 5 | 6 | 8 | 6 | |
| 23 - Rescue Mission | PolishDeliveryNo lens is broken, but Design and Involvement are soft — this reads as a polish pass. | SoftThe structure works but is leaking power in places. | 6 | 7 / 7 | 6 / 6 | 6 | 7 | 5 | 6 | 5 | 5 | 7 | 5 | 4 | 6 | 7 | 4 | 5 | 6 | 5 | 6 | 8 | 6 | |
| 24 - Ramonda's Ultimatum | KeepNegotiationAll three lenses are solid — worth protecting as it stands. | SolidThe story machine is built and mostly working. | 7 | 8 / 8 | 8 / 8 | 7 | 7 | 6 | 7 | 6 | 6 | 8 | 7 | 7 | 8 | 8 | 6 | 7 | 7 | 7 | 7 | 8 | 7 | |
| 25 - untitled | KeepInvestigationAll three lenses are solid — worth protecting as it stands. | SolidThe story machine is built and mostly working. | 7 | 8 / 8 | 7 / 7 | 7 | 7 | 6 | 7 | 6 | 6 | 8 | 6 | 5 | 7 | 8 | 5 | 7 | 6 | 6 | 6 | 8 | 7 | |
| 26 - Captives and Culture | PolishOrientationNo lens is broken, but Design and Involvement are soft — this reads as a polish pass. | SoftThe structure works but is leaking power in places. | 7 | 8 / 7 | 7 / 7 | 7 | 6 | 7 | 7 | 6 | 6 | 7 | 6 | 5 | 6 | 7 | 5 | 6 | 7 | 6 | 7 | 8 | 6 | |
| 27 - Namor's Custody | Low on its ownDeliveryDesign and Involvement are broken — this reads as a rebuild before polish. | BrokenThe underlying story machine isn’t holding — worth looking at before polish. | 7 | 7 / 6 | 6 / 6 | 7 | 6 | 8 | 7 | 6 | 5 | 5 | 4 | 3 | 4 | 6 | 5 | 5 | 5 | 5 | 5 | 7 | 5 | |
| 28 - Namor's Origin Story | ReworkMontageInvolvement is broken — a load-bearing lens isn’t doing its job yet. | SoftThe structure works but is leaking power in places. | 7 | 8 / 8 | 7 / 7 | 8 | 7 | 8 | 7 | 6 | 5 | 6 | 6 | 5 | 7 | 7 | 6 | 7 | 5 | 7 | 6 | 8 | 7 | |
| 29 - Namor's Duty | PolishDeliveryNo lens is broken, but Design and Involvement are soft — this reads as a polish pass. | SoftThe structure works but is leaking power in places. | 7 | 8 / 7 | 6 / 7 | 7 | 7 | 7 | 7 | 6 | 5 | 8 | 6 | 5 | 6 | 8 | 5 | 5 | 6 | 6 | 6 | 8 | 6 | |
| 30 - Revelations in Talocan | PolishInvestigationNo lens is broken, but Involvement is soft — this reads as a polish pass. | SolidThe story machine is built and mostly working. | 7 | 7 / 6 | 5 / 6 | 7 | 6 | 7 | 7 | 6 | 5 | 6 | 4 | 3 | 5 | 6 | 4 | 6 | 6 | 6 | 5 | 7 | 5 | |
| 31 - Infiltrating the NSA Facility | PolishDeliveryNo lens is broken, but Design and Involvement are soft — this reads as a polish pass. | SoftThe structure works but is leaking power in places. | 6 | 8 / 8 | 6 / 7 | 6 | 7 | 5 | 6 | 5 | 4 | 8 | 6 | 5 | 7 | 7 | 5 | 4 | 6 | 6 | 7 | 8 | 6 | |
| 32 - Retrieving the Thumb Drive | KeepDeliveryAll three lenses are solid — worth protecting as it stands. | SolidThe story machine is built and mostly working. | 7 | 8 / 8 | 6 / 7 | 7 | 7 | 6 | 7 | 6 | 5 | 8 | 6 | 5 | 6 | 8 | 5 | 4 | 6 | 6 | 7 | 8 | 7 | |
| 33 - Mission to Talocan | ReworkDeliveryInvolvement is broken — a load-bearing lens isn’t doing its job yet. | SoftThe structure works but is leaking power in places. | 6 | 7 / 6 | 6 / 6 | 7 | 6 | 6 | 7 | 5 | 5 | 7 | 5 | 4 | 5 | 7 | 4 | 4 | 6 | 5 | 5 | 7 | 5 | |
| 34 - Alliances and Ultimatums | KeepNegotiationAll three lenses are solid — worth protecting as it stands. | SolidThe story machine is built and mostly working. | 7 | 7 / 8 | 7 / 7 | 7 | 7 | 7 | 7 | 6 | 6 | 8 | 7 | 8 | 8 | 8 | 6 | 7 | 7 | 7 | 6 | 6 | 7 | |
| 35 - Escape from the Talocanil Cave | PolishRescueNo lens is broken, but Execution and Involvement are soft — this reads as a polish pass. | SolidThe story machine is built and mostly working. | 6 | 8 / 7 | 7 / 7 | 6 | 7 | 5 | 6 | 5 | 5 | 8 | 6 | 5 | 7 | 8 | 6 | 5 | 6 | 6 | 7 | 8 | 6 | |
| 36 - Return to Wakanda | PolishAftermathNo lens is broken, but Design, Execution and Involvement are soft — this reads as a polish pass. | SoftThe structure works but is leaking power in places. | 6 | 7 / 7 | 6 / 7 | 6 | 6 | 5 | 6 | 5 | 5 | 7 | 4 | 3 | 5 | 7 | 4 | 6 | 5 | 5 | 6 | 8 | 6 | |
| 37 - Namor's Betrayal | PolishDeliveryNo lens is broken, but Design, Execution and Involvement are soft — this reads as a polish pass. | SoftThe structure works but is leaking power in places. | 7 | 8 / 8 | 7 / 8 | 7 | 7 | 6 | 7 | 6 | 6 | 8 | 7 | 6 | 8 | 8 | 5 | 6 | 7 | 7 | 7 | 8 | 7 | |
| 38 - Threats and Escapes | PolishAftermathNo lens is broken, but Design, Execution and Involvement are soft — this reads as a polish pass. | SoftThe structure works but is leaking power in places. | 6 | 7 / 6 | 5 / 6 | 6 | 6 | 5 | 7 | 6 | 5 | 6 | 4 | 3 | 5 | 6 | 4 | 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. | 7 | 7 / 7 | 7 / 7 | 6 | 7 | 5 | 7 | 6 | 5 | 7 | 6 | 5 | 7 | 8 | 5 | 6 | 7 | 6 | 6 | 8 | 6 | |
| 40 - Attack on the Golden City | PolishAftermathNo lens is broken, but Design, Execution and Involvement are soft — this reads as a polish pass. | SoftThe structure works but is leaking power in places. | 7 | 8 / 8 | 8 / 8 | 7 | 7 | 6 | 7 | 6 | 5 | 8 | 7 | 6 | 8 | 8 | 6 | 7 | 7 | 7 | 8 | 8 | 7 | |
| 41 - Under Attack | ReworkPursuitInvolvement is broken — a load-bearing lens isn’t doing its job yet. | SoftThe structure works but is leaking power in places. | 6 | 7 / 7 | 7 / 7 | 6 | 6 | 5 | 6 | 5 | 4 | 7 | 7 | 6 | 7 | 7 | 5 | 6 | 5 | 7 | 7 | 8 | 6 | |
| 42 - Namor Attacks | PolishPursuitNo lens is broken, but Design, Execution and Involvement are soft — this reads as a polish pass. | SoftThe structure works but is leaking power in places. | 7 | 8 / 8 | 8 / 8 | 7 | 7 | 6 | 7 | 6 | 5 | 8 | 8 | 8 | 8 | 8 | 7 | 7 | 6 | 8 | 8 | 8 | 7 | |
| 43 - Namor Attacks | KeepAftermathAll three lenses are solid — worth protecting as it stands. | SolidThe story machine is built and mostly working. | 7 | 8 / 9 | 9 / 9 | 7 | 8 | 6 | 7 | 7 | 5 | 8 | 8 | 7 | 9 | 9 | 6 | 9 | 6 | 8 | 8 | 8 | 7 | |
| 44 - Shuri's Grief | PolishAftermathNo lens is broken, but Involvement is soft — this reads as a polish pass. | SolidThe story machine is built and mostly working. | 7 | 9 / 8 | 7 / 7 | 7 | 6 | 6 | 7 | 7 | 8 | 5 | 7 | 6 | 8 | 7 | 5 | 8 | 7 | 7 | 7 | 8 | 7 | |
| 45 - Mourning and Decision Making | KeepRelationship shiftAll three lenses are solid — worth protecting as it stands. | SolidThe story machine is built and mostly working. | 7 | 8 / 8 | 6 / 7 | 7 | 6 | 6 | 8 | 6 | 7 | 5 | 7 | 7 | 6 | 7 | 5 | 7 | 7 | 6 | 6 | 8 | 7 | |
| 46 - Tribal Council Meeting and Okoye's Offer | PolishRelationship shiftNo lens is broken, but Design, Execution and Involvement are soft — this reads as a polish pass. | SoftThe structure works but is leaking power in places. | 6 | 7 / 7 | 6 / 7 | 6 | 6 | 5 | 7 | 6 | 6 | 7 | 6 | 5 | 7 | 6 | 5 | 6 | 6 | 6 | 6 | 7 | 6 | |
| 47 - Shuri's Call with Ross | PolishDeliveryNo lens is broken, but Design and Involvement are soft — this reads as a polish pass. | SoftThe structure works but is leaking power in places. | 6 | 8 / 8 | 7 / 7 | 6 | 7 | 5 | 7 | 6 | 5 | 8 | 6 | 5 | 7 | 8 | 6 | 7 | 6 | 6 | 7 | 8 | 6 | |
| 48 - Building A Plan | KeepInvestigationAll three lenses are solid — worth protecting as it stands. | SolidThe story machine is built and mostly working. | 7 | 8 / 8 | 8 / 8 | 7 | 7 | 6 | 7 | 7 | 6 | 8 | 7 | 6 | 8 | 8 | 6 | 7 | 7 | 7 | 7 | 8 | 7 | |
| 49 - Shuri's Revenge Plan | PolishMontageNo lens is broken, but Design, Execution and Involvement are soft — this reads as a polish pass. | SoftThe structure works but is leaking power in places. | 7 | 7 / 7 | 6 / 6 | 7 | 7 | 6 | 7 | 7 | 7 | 8 | 4 | 3 | 5 | 8 | 4 | 5 | 6 | 5 | 6 | 8 | 6 | |
| 50 - The Heart-Shaped Herb | KeepRitualAll three lenses are solid — worth protecting as it stands. | SolidThe story machine is built and mostly working. | 7 | 8 / 8 | 7 / 7 | 7 | 7 | 6 | 7 | 7 | 7 | 8 | 5 | 4 | 7 | 8 | 5 | 7 | 6 | 6 | 6 | 8 | 7 | |
| 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 | 9 / 9 | 8 / 8 | 7 | 6 | 7 | 8 | 7 | 8 | 5 | 8 | 7 | 8 | 6 | 7 | 8 | 8 | 8 | 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. | 6 | 8 / 7 | 7 / 7 | 7 | 6 | 6 | 7 | 6 | 7 | 6 | 6 | 5 | 7 | 7 | 5 | 6 | 6 | 7 | 6 | 8 | 6 | |
| 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 | 8 / 8 | 7 / 7 | 7 | 6 | 6 | 7 | 6 | 7 | 7 | 7 | 7 | 8 | 7 | 6 | 7 | 7 | 7 | 6 | 8 | 6 | |
| 54 - Pre-Battle Preparations | PolishDeliveryNo lens is broken, but Design, Execution and Involvement are soft — this reads as a polish pass. | SoftThe structure works but is leaking power in places. | 7 | 8 / 7 | 7 / 7 | 7 | 7 | 6 | 7 | 6 | 7 | 8 | 6 | 5 | 7 | 8 | 5 | 7 | 7 | 6 | 6 | 8 | 6 | |
| 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 | 8 / 7 | 6 / 7 | 6 | 6 | 5 | 6 | 5 | 4 | 7 | 6 | 5 | 7 | 7 | 4 | 3 | 5 | 5 | 7 | 8 | 6 | |
| 56 - The Black Panther vs. Namor | PolishPursuitNo lens is broken, but Design, Execution and Involvement are soft — this reads as a polish pass. | SoftThe structure works but is leaking power in places. | 7 | 8 / 9 | 8 / 8 | 7 | 7 | 6 | 7 | 6 | 6 | 8 | 8 | 8 | 8 | 8 | 7 | 7 | 8 | 8 | 8 | 9 | 8 | |
| 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 | 6 / 7 | 7 / 7 | 6 | 7 | 5 | 5 | 4 | 3 | 7 | 7 | 7 | 8 | 8 | 6 | 5 | 5 | 6 | 7 | 5 | 6 | |
| 58 - Midnight Angels Strike Back | KeepContestAll three lenses are solid — worth protecting as it stands. | SolidThe story machine is built and mostly working. | 7 | 8 / 8 | 8 / 8 | 7 | 7 | 6 | 7 | 6 | 6 | 8 | 8 | 7 | 8 | 8 | 7 | 7 | 7 | 8 | 8 | 8 | 7 | |
| 59 - The Battle For Survival | PolishContestNo lens is broken, but Design, Execution and Involvement are soft — this reads as a polish pass. | SoftThe structure works but is leaking power in places. | 6 | 8 / 8 | 8 / 8 | 7 | 6 | 6 | 6 | 6 | 5 | 7 | 8 | 8 | 7 | 7 | 7 | 7 | 5 | 8 | 8 | 6 | 7 | |
| 60 - The Battle for Wakanda | PolishContestNo lens is broken, but Design, Execution and Involvement are soft — this reads as a polish pass. | SoftThe structure works but is leaking power in places. | 6 | 7 / 8 | 8 / 8 | 7 | 6 | 5 | 7 | 6 | 5 | 7 | 8 | 7 | 8 | 7 | 6 | 7 | 6 | 8 | 7 | 6 | 7 | |
| 61 - Confrontation and Yield | KeepDeliveryAll three lenses are solid — worth protecting as it stands. | SolidThe story machine is built and mostly working. | 7 | 8 / 9 | 8 / 8 | 7 | 7 | 6 | 7 | 8 | 7 | 8 | 8 | 7 | 9 | 8 | 6 | 8 | 8 | 8 | 7 | 9 | 8 | |
| 62 - Val confronts Ross | KeepDeliveryAll three lenses are solid — worth protecting as it stands. | SolidThe story machine is built and mostly working. | 7 | 9 / 9 | 8 / 8 | 7 | 7 | 6 | 7 | 6 | 5 | 7 | 8 | 8 | 7 | 8 | 7 | 6 | 8 | 8 | 8 | 9 | 8 | |
| 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 | 8 / 7 | 6 / 7 | 6 | 6 | 4 | 6 | 5 | 4 | 7 | 6 | 5 | 6 | 7 | 5 | 5 | 4 | 6 | 7 | 8 | 6 | |
| 64 - Repentance and Redemption | PolishAftermathNo lens is broken, but Design and Involvement are soft — this reads as a polish pass. | SoftThe structure works but is leaking power in places. | 6 | 7 / 7 | 5 / 6 | 6 | 6 | 5 | 7 | 6 | 5 | 6 | 5 | 4 | 5 | 7 | 4 | 5 | 5 | 5 | 6 | 8 | 6 | |
| 65 - The Throne Challenge | PolishRitualNo lens is broken, but Design and Involvement are soft — this reads as a polish pass. | SoftThe structure works but is leaking power in places. | 6 | 8 / 7 | 4 / 5 | 7 | 6 | 7 | 7 | 6 | 5 | 7 | 4 | 3 | 5 | 6 | 4 | 4 | 5 | 4 | 5 | 8 | 5 | |
| 66 - Farewell and New Beginnings | KeepDeliveryAll three lenses are solid — worth protecting as it stands. | SolidThe story machine is built and mostly working. | 7 | 8 / 7 | 7 / 7 | 7 | 6 | 5 | 8 | 8 | 8 | 4 | 4 | 3 | 5 | 6 | 6 | 7 | 6 | 6 | 5 | 8 | 6 | |
| 67 - Family Secrets Revealed | PolishDeliveryNo lens is broken, but Design and Involvement are soft — this reads as a polish pass. | SoftThe structure works but is leaking power in places. | 8 | 9 / 9 | 6 / 7 | 8 | 7 | 7 | 8 | 8 | 8 | 5 | 3 | 2 | 4 | 8 | 7 | 8 | 7 | 8 | 7 | 8 | 8 | |
“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 powerful emotional beat that makes the reader want to continue. The death of T'Challa is a major event, and the reader is compelled to see how Shuri and Wakanda will cope. The scene also sets up the film's central conflict (grief and legacy). The only minor note is that the scene is a prologue, so the reader knows the story will continue, but the emotional hook is strong.
This scene establishes the emotional and narrative foundation for the entire script. It sets up Shuri's grief, her relationship with her mother, and the loss of the Black Panther. The momentum is strong because the reader wants to see how Shuri will evolve from this point. The scene also introduces key elements (the Heart-Shaped Herb, the lab, Griot) that will be important later. The script momentum is 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 is emotionally resonant and sets up Shuri's arc, but it doesn't create a strong pull to the next scene. The global reactions provide a sense of closure, and the scene ends on a somber note. The reader is likely to continue for the story's sake, but the scene itself doesn't end on a cliffhanger or a question that demands an answer.
Up to this point, the script has established T'Challa's death and Shuri's grief. The funeral scene reinforces the emotional stakes but doesn't advance the plot significantly. The momentum is carried by the emotional weight and the promise of future conflict (the UN hearing, the vibranium detector). The scene is a necessary beat but not a driver of 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 compels the reader to continue by establishing a clear conflict and hinting at larger threats. Ramonda's line about 'whispers' that 'Now is our time to strike' creates anticipation for how Wakanda will respond. The Mali intercut adds a sense of immediate danger. The scene ends on a strong note, making the reader want to see what happens next.
Up to this point, the script has established T'Challa's death, the funeral, and now the political pressure on Wakanda. This scene adds a new layer of conflict and sets up the threat of external forces. The momentum is building, with the Mali intercut hinting at covert operations. The scene contributes to the overall narrative momentum by raising the stakes and introducing the theme of Wakanda's vulnerability.
“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 strong hook: the cargo ship and the vibranium detector, which promises a new threat. The reader is compelled to keep reading to see what happens next. The scene's combination of action and political intrigue maintains interest.
The scene builds on the previous scenes' momentum, showing Wakanda's proactive response to the threats established earlier. It also introduces a new plot thread (the cargo ship) that will likely lead to the next conflict. The script's momentum is maintained, though the scene doesn't dramatically escalate the stakes beyond what's already been established.
“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—the blue-skinned woman on the boat deck—which compels the reader to continue. The deaths of the divers create a sense of danger that makes the reader want to know what happens next. The scene effectively raises questions: Who are these people? What do they want? The reader is invested in the mystery.
This scene contributes to the script's momentum by introducing a new threat and raising the stakes. It follows the previous scene's setup (the mining operation) and leads into the next scene (the attack on the boat). The scene is a turning point that shifts the plot from discovery to conflict. However, the momentum is somewhat generic—it's a standard 'horror set piece' that doesn't yet connect to the larger themes of the script (grief, legacy).
“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: the sirens breach again and start to sing a new melody, and Dr. Graham is escaping in the helicopter. This creates a strong pull to the next scene, where we expect to see Namor. The scene's escalating action and the mystery of the Talocanil make the reader want to continue.
Up to this point, the script has established the Talocanil threat and the global stakes. This scene advances the plot by showing the Talocanil's power and the humans' vulnerability, setting up the conflict with Wakanda. The momentum is strong, though the scene is more of a set piece than a character-driven beat. The script's overall momentum is maintained by the escalating action and the promise of Namor's reveal.
“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 the reader to continue: the helicopter's destruction is a shocking event, and the newscaster's report about the UN and the succession creates intrigue. The reader wants to know how Wakanda will respond to this new threat. The scene effectively sets up the next conflict.
Up to this point, the script has established the threat of Namor and the Talocanil, and this scene escalates that threat by showing their power. The momentum is strong, with the action and political intrigue building. The scene maintains the script's forward drive, though the newscaster's exposition momentarily pauses the action.
“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 makes the reader want to continue because it deepens our understanding of Shuri's emotional state and sets up the next scene (the drive and the ritual). The emotional stakes are high, and the reader is invested in Shuri's journey. However, the scene itself is not a page-turner; it's a character moment that builds anticipation for what comes next.
Up to this point, the script has established Shuri's grief and her avoidance, and this scene reinforces that while also introducing the possibility of healing. The scene contributes to the overall momentum by setting up the ritual that will be central to Shuri's arc. It doesn't advance the plot significantly, but it deepens the character, which is essential for the emotional payoff later.
“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 emotional note that makes the reader want to see what happens next, especially with the impending arrival of Namor. The emotional depth of the scene creates investment in Shuri's journey. The scene is compelling, though the slow pacing in the middle might cause some readers to lose momentum. Overall, it effectively compels the reader to continue.
Up to this point, the script has established Shuri's grief and her resistance to healing, which is a strong foundation for her arc. This scene deepens that foundation and sets up the conflict with Namor. The script's momentum is steady, with a clear emotional throughline. The scene contributes to the overall narrative by advancing Shuri's character development, which is essential for the story's emotional 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.
The scene ends on a strong hook: the VB detector appearing by the fire, dripping with water, is a visual and narrative cliffhanger. The reader is compelled to keep reading to find out what it means, how they will respond, and what Namor's next move will be. The scene's momentum is strong.
Up to this point, the script has established a strong emotional foundation (T'Challa's death, Shuri's grief) and a growing external threat (the UN, the mining ship, the Talocanil). This scene escalates the threat by introducing Namor directly, and the momentum is maintained. The script is building towards a major conflict, and this scene is a key turning point. 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 is moderately compelling. The reader wants to know what the council decides, but the scene doesn't create a strong pull to keep reading. The debate is predictable, and the ending—Ramonda considering—is a soft cliffhanger. The reader is likely to continue but not with a strong sense of urgency or anticipation.
The scene maintains the script's momentum. It's a necessary beat in the story, setting up the central conflict and the council's response. It doesn't stall the plot, but it also doesn't accelerate it. The scene is a functional bridge between the discovery of Namor and the next action beat. The reader is likely to continue, but the scene doesn't create a strong sense of forward motion.
“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 setup for the next scene (Ross's jog), but it doesn't create a strong pull. The decision to go is made, but the reader isn't desperate to see what happens next. The scene lacks a hook—a question, a threat, or an emotional cliffhanger.
The scene advances the plot—it sets up the mission to find the scientist—and maintains the script's momentum. However, it doesn't add much emotional or thematic momentum. The scene is a functional bridge, but it could do more to deepen Shuri's arc and the central conflict with Namor.
“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 hook—Riri's 'WHAT?!' after learning about the merman—which makes the reader want to see what happens next. However, the middle of the scene is less compelling, and the reader might lose some momentum during the Ross conversation. The scene does its job of setting up the next conflict, but it doesn't create a burning desire to turn the page.
Up to this point, the script has been building momentum through the introduction of Namor, the attack on the cargo ship, and the political tension. This scene advances the plot by introducing Riri and setting up the next conflict. It maintains the script's momentum, though it's a quieter scene compared to the action that came before. The reader is likely to keep reading to see how the confrontation with Namor unfolds.
“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: the Kimoyo bead attaches to the armored car, setting up the escape. The reader is compelled to continue to see how they get out. The tension is high, and the scene's resolution is deferred, creating anticipation.
Up to this point, the script has built momentum through the introduction of Namor, the threat to Wakanda, and the mission to find Riri. This scene advances the plot by bringing the characters together and setting up the escape, which will lead to the confrontation with Namor. 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 on a strong action beat—the Barracuda crashing through the garage door—and the intercuts with the armored car create a sense of momentum. The reader is compelled to keep reading to see if they escape and what happens next with the police and Namor.
Up to this point, the script has built momentum through the escalating threat of Namor and the mission to protect Riri. This scene maintains that momentum with a fun, action-packed escape that also advances the characters' relationships. The reader is invested in seeing how the escape plays out and what happens next.
“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—Okoye's 'Shuri, where are you?'—which makes the reader want to continue to see if they reunite. The action is engaging and the intercutting creates a sense of urgency. The scene is a page-turner, even if it's a standard chase.
Up to this point, the script has built momentum through the chase and the introduction of Riri. This scene maintains that momentum, but it doesn't significantly advance the plot—it's a set piece. The reader is compelled to keep reading because of the action and the cliffhanger, but the scene doesn't introduce new information or raise the stakes beyond the immediate escape. The momentum is steady, not escalating.
“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 is compelling. The chase is exciting, and the cutaway to Riri taking out the drone creates a satisfying payoff. The scene ends on a cliffhanger (Shuri warning Riri about the oxygen), which makes the reader want to continue to see if Riri succeeds. The scene is a strong page-turner.
The scene contributes to the script's momentum by advancing the escape sequence and setting up the next scene (Riri's suit and the drone). It maintains the fast pace of the action and keeps the plot moving. The scene is a solid part of the larger chase sequence, and it builds on the tension established in previous scenes.
“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 is engaging enough to keep reading, but it doesn't create a strong pull to the next page. The action is resolved, and the next beat (the blockade) is set up, but there's no cliffhanger or emotional hook. The reader is likely to continue because of the overall story, not this scene alone.
Up to this point, the script has built momentum through the chase sequence, and this scene maintains that momentum. The action is consistent with the previous scenes, and the stakes are clear. The scene doesn't stall the narrative; it propels it forward toward the next obstacle.
“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 hook: Shuri is captured, Riri is about to be taken, and the reader wants to know what happens next. The action and stakes compel the reader to continue. The only slight dip is the middle fight, but the ending is effective.
Up to this point, the script has built momentum through the chase and the escalating threat of the Talocanil. This scene raises the stakes by capturing Shuri, which will drive the next act. The momentum is strong, and the reader is invested in the outcome.
“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 does compel the reader to keep reading, mainly because of the unresolved tension: Ross has the bracelet, Val is suspicious, and the ride to the office promises more conflict. The scene ends on a note of anticipation. The reader wants to know what happens next, both in the immediate scene (the car ride) and in the larger plot (the investigation).
The scene maintains the script's momentum by advancing the plot (the US investigation) and setting up future conflicts (Ross's ride with Val, the search for Shuri). It also raises the stakes for the characters. The scene is a necessary beat in the larger narrative, and it does its job of keeping the story moving.
“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 strong hook: Okoye is stripped of her rank, and Ramonda is left grieving. The reader is compelled to continue to see how Okoye will react and what will happen to Shuri. The transition to the lab scene, where Ramonda discovers Shuri's recording, adds another layer of intrigue.
This scene is a pivotal moment in the script, raising the stakes for Okoye and deepening Ramonda's grief. It maintains the script's momentum by setting up Okoye's potential redemption arc and the ongoing search for Shuri. The scene's emotional weight carries forward, making the reader invested in the characters' fates.
“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 doesn't create a strong pull to keep reading. The tension is brief, and the resolution is too neat. The Ramonda call is a letdown—it's mostly exposition. The scene feels like a bridge, not a hook.
The scene advances the plot (Ross gets the beads, talks to Ramonda) but doesn't add significant momentum. It's a necessary scene but not a driving one. The script's overall momentum is strong, but this scene is a dip.
“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 strong visual hook—Ramonda blowing the conch and throwing it into the ocean—which compels the reader to continue. However, the scene itself is not particularly gripping; the conversation is calm and informational. The hook is effective, but the scene could do more to build anticipation.
The scene advances the plot by establishing the alliance between Ramonda and Ross and setting up the laptop subplot. It also transitions to the beach scene, which is a new location and a new development. The momentum is steady but not strong; the scene is a necessary step but doesn't add significant urgency.
“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 strong hook: Ramonda's prayer to Bast and her decision to seek Nakia's help. This creates anticipation for the next scene, as we wonder if Nakia can rescue Shuri in time. The scene's tension and the unresolved threat compel the reader to continue.
Up to this point, the script has built momentum through a series of escalating conflicts: the UN hearing, the attack on the cargo ship, the introduction of Namor, and now this direct confrontation. The scene advances the plot by setting up the rescue mission and raising the stakes for the upcoming conflict. The script's momentum is strong, with each scene leading logically to the next.
“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 strong hook: the Mayan Elder's warning about K'uk'ulkan and the danger of searching for him. This creates anticipation for the next scene, where Nakia will presumably find the beach and encounter Namor. The scene also leaves the reader wanting to know how Nakia will rescue Shuri. The scene is compelling and makes the reader want to continue.
The scene advances the plot by setting up Nakia's mission and introducing the Mayan Elder as a guide. It also deepens the emotional stakes and reinforces the threat of Namor. The scene maintains the script's momentum by moving from the personal (Ramonda's plea) to the mythic (the Elder's story), keeping the reader engaged. The script's overall momentum is strong, and this scene contributes to it.
“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 does make the reader want to continue. The mystery of the cave, the threat of Namor, and the dynamic between Shuri and Riri are all compelling. The scene ends with Shuri being led to Namor, which is a strong hook. However, the scene could be more compelling if it ended on a more specific question or a moment of higher tension.
This scene is part of a larger narrative, and it does contribute to the momentum. It moves Shuri from captivity to a meeting with Namor, which is a key plot point. The scene also develops the Shuri-Riri relationship, which is important for the story. However, the scene doesn't add much new information or raise the stakes significantly; it's more of a transition scene. The momentum is maintained but not accelerated.
“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 is compelling because of the content of the backstory. The audience wants to know how Namor became who he is. However, the scene itself does not create a strong pull to keep reading. The present-tense interaction is static, and the scene ends with the flashback, which is a natural stopping point. The scene does not end on a cliffhanger or a question that demands an answer. The audience is left with a sense of completion, not anticipation.
Up to this point, the script has been building momentum through action and political intrigue. This scene is a deliberate pause for exposition and character development. It is a necessary scene, but it does slow the momentum. The scene is a 'breather' in the narrative, and it is placed at a point where the audience is invested enough to tolerate a slower pace. The scene does not derail the momentum, but it does not add to it.
“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 the reader to continue because it deepens Namor's character and sets up his conflict with Wakanda. The friar's curse is a hook that makes us want to see how it plays out. The montage's brisk pace keeps the story moving, and the emotional beats make us care about Namor.
Up to this point, the script has established Shuri's grief, the threat of Namor, and the political tensions. This backstory scene adds depth to Namor, making him a more sympathetic antagonist. It maintains the script's momentum by explaining his motivations, which will pay off in the final confrontation. The scene doesn't stall the plot; it enriches it.
“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 creates some curiosity about Talocan, but it doesn't create a strong compulsion to keep reading. The negotiation is resolved, and the scene ends with a setup for the underwater city, which is a visual spectacle but not a dramatic cliffhanger. The audience might want to see Talocan, but the emotional stakes are low. The scene doesn't end with a question or a threat that makes the reader eager to turn the page.
Up to this point, the script has built momentum through the conflict with Namor, the abduction of Shuri and Riri, and the threat to Wakanda. This scene continues that momentum by setting up the alliance and the tour of Talocan, which is a key worldbuilding moment. The scene doesn't stall the plot; it advances the relationship between Shuri and Namor, which is central to the story. The momentum is maintained, though not significantly increased.
“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 is beautiful but not gripping. The tour structure and lack of conflict make it easy to put down. The offer at the end ('Nothing') is a mild hook, but it doesn't create a strong desire to know what happens next. The reader might be curious about the Sastun project, but the scene doesn't end on a cliffhanger or a question.
Up to this point, the script has built momentum through action and political intrigue. This scene is a breather, a worldbuilding pause. It doesn't advance the plot much, but it deepens Namor's character and sets up the Sastun project, which will be important later. The momentum is maintained by the promise of future conflict, but this scene itself is a lull.
“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 ('Off the guard’s look...') which is a classic hook, but the hook is weak because the guard's look is generic. The reader is mildly curious but not desperate to know what happens next. The scene's brevity and lack of tension reduce its pull.
The scene advances the plot: it sets up the infiltration mission that will lead to the laptop's destruction. It's a necessary step in the larger narrative, and the reader is invested in the overall story. The scene's brevity keeps the momentum moving, even if the scene itself is not a standout.
“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 is competent and moves the plot forward, but it doesn't create a strong desire to keep reading. The mission is successful, but the lack of tension or emotional stakes makes it feel like a checkbox. The reader is likely to continue because of the larger plot, not because of this scene's hook.
The scene contributes to the overall momentum of the script by advancing the subplot of destroying the laptop and protecting Wakanda. It's a necessary step in the larger narrative. The scene doesn't stall the plot, but it also doesn't add significant momentum on its own. The reader is likely to continue because of the main storyline, not this scene.
“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 creates some forward momentum—the audience wants to know if Shuri's plan will work and if Nakia will rescue her. But the scene's middle section is flat, and the intercut with Nakia feels like a separate scene. The ending ('Let us watch the sastun rise') is a hook, but it's not a strong one. The scene doesn't make the reader desperate to turn the page.
The scene contributes to the script's momentum by advancing the plot—Shuri's plan is set in motion, and Nakia's rescue is underway. But the scene doesn't add much emotional or thematic momentum. It's a functional step in the story, not a turning point. The script's overall momentum is strong, but this scene is a lull.
“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 strong hook: Namor's threat to verify Ramonda's claim and the implication that he will attack. The B134 block raises the stakes and leaves the reader wanting to know what happens next. The scene is compelling, but the middle section (A134) could be more gripping. Overall, the scene does its job of propelling the reader forward.
Up to this point, the script has built a complex conflict with multiple factions. This scene advances the plot by solidifying Namor's threat and setting up the attack on Wakanda. The momentum is strong, but the scene's dialogue-heavy middle could slow the reader's engagement. The script's overall momentum is maintained by the high stakes and the emotional arc.
“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—the escape is underway, and the audience wants to know if they'll make it. The rescue is a satisfying turn, but the scene doesn't create a strong desire to see what happens next beyond the immediate action.
The scene maintains the script's momentum by moving the plot forward—Shuri and Riri are rescued, and the story can progress. The scene doesn't stall, but it also doesn't add significant new information or character development. It's a functional bridge scene.
“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 does compel the reader to continue, mainly because of the unresolved threads: Okoye's demotion, Namor's inevitable retaliation, and Shuri's determination to get to her lab. The scene ends with a clear forward motion ('I need to get to my lab'), which hints at the next step. However, the scene itself is not a page-turner; it's a calm moment that relies on the audience's investment in the characters.
The script's momentum is strong overall. This scene is a necessary beat in the larger narrative, and it maintains the forward drive by resolving the rescue and setting up the next conflict. The scene doesn't stall the plot; it moves it forward. The momentum is carried by the unresolved threads and the audience's investment in Shuri's arc.
“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 the reader to continue because it sets up a major conflict and raises the stakes. The reader wants to see how Wakanda will respond to Namor's threat. The scene is a strong turning point, though it's not the most gripping scene in the script—it's more of a setup than a cliffhanger. The reader is invested in the outcome.
Up to this point, the script has built momentum through Shuri's capture, escape, and the escalating threat of Namor. This scene solidifies the antagonist's resolve and sets the stage for the climactic battle. The script's momentum is strong, and this scene maintains it by raising the stakes and moving the plot forward. The reader is eager to see the 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 a Siren sighting, which is a hook, but the preceding beats are low-energy. The reader is mildly curious about the Siren but not compelled by the characters' emotional states. The scene feels like a pause rather than a turning point.
Up to this point, the script has built momentum through action and political intrigue. This scene is a necessary breather, but it doesn't add much momentum. It confirms Shuri's safety and sets up the next attack, but the emotional beats are underdeveloped.
“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 strong hook: 'We're under attack.' This compels the reader to continue to see how the characters respond. The emotional investment in Okoye and Nakia also makes the reader want to see them survive. The scene is effective in driving the narrative forward.
This scene is a turning point in the script, moving from character development to the major action set piece. It maintains the script's momentum by setting up the attack on Wakanda. The scene is effective in transitioning the narrative into the climax.
“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 strong hook: Ramonda and Riri are now piloting the rescue fleet, and the attack is escalating. The reader wants to know if they can save the city and what happens to Shuri. The scene compels the reader to continue.
Up to this point, the script has built momentum through the escalating conflict with Namor and the personal stakes for Shuri and Ramonda. This scene continues that momentum, raising the stakes and setting up the next phase of the attack. The script is compelling and the reader is invested in the outcome.
“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 Talon Fighters raining fire on Talocanil warriors, which is a strong action beat that makes the reader want to see the outcome. The appearance of Namor walking toward the palace creates anticipation for a confrontation. The scene's fast pace and high stakes keep the reader engaged. However, the scene is part of a longer battle, so the compulsion to keep reading is more about the overall battle than this specific scene's cliffhanger.
The scene contributes to the script's momentum by escalating the attack and moving Namor closer to the palace. The battle is a major turning point in the story, and this scene shows the scale of the threat. The momentum is strong, but it's part of a longer sequence, so the scene itself doesn't provide a major shift in the story's direction. The momentum is maintained by the action and the clear progression toward a 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 on a strong cliffhanger: Namor's spear cracks the glass but holds, and Griot announces one minute until the last scarab beetle is safe. The reader is compelled to continue to see if the glass breaks and what happens to Ramonda and Riri. The action is engaging and the stakes are high.
Up to this point, the script has built momentum through the attack on Wakanda, and this scene escalates it further. The reader is invested in the outcome of the battle and the fate of the royal family. The scene maintains the script's momentum by raising the stakes and setting up the next 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 on a powerful cliffhanger: the Queen is dead, and Namor has issued an ultimatum. The reader is compelled to continue to see how Shuri will respond and whether Wakanda will fall. The emotional stakes are so high that it's impossible not to want to know what happens next.
Up to this point, the script has built momentum through escalating conflicts and emotional stakes. This scene is a major turning point that propels the narrative into its final act. The death of the Queen raises the stakes for Shuri's transformation into the Black Panther, and the reader is invested in seeing how she will avenge her mother. The script's momentum is strong, and this scene is a key driver.
“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's emotional intensity and the question of whether Shuri will survive compel the reader to continue. The resolution—Shuri choosing to live—creates a natural curiosity about what she will do next. The scene ends on a note of tentative hope, but the reader is aware that the larger conflict with Namor is unresolved, which drives momentum.
Up to this point, the script has been building toward Shuri's lowest point. This scene is a crucial turning point in her arc, moving her from passive grief to a potential active role. The scene's resolution—Shuri choosing to live—sets up her transformation into the Black Panther. The momentum is strong, as the reader is invested in Shuri's journey and eager to see how she will confront Namor.
“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 is emotionally compelling, but it doesn't create a strong pull to keep reading. The conversation is self-contained, and the ending—M'Baku walking away—feels like a natural pause. The transition to the hydrobomb discovery provides a new plot thread, but it's a separate scene. The scene could be more compelling if it ended on a more active or intriguing note, such as Shuri making a decision that has immediate consequences.
The scene contributes to the script's momentum by solidifying Shuri's motivation and setting up the next phase of the plot (the evacuation and the hydrobomb). The scene is a necessary beat in Shuri's arc, moving her from grief to a thirst for vengeance. The script's momentum is maintained, though this scene is more of a character beat than a plot driver.
“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 considering the offer, which is a decent hook. However, the council scene is slow, and the reader might lose interest before reaching the more compelling Okoye scene. The scene doesn't end on a strong cliffhanger—it's a thoughtful pause.
Up to this point, the script has been building toward the confrontation with Namor. This scene maintains that momentum by showing the political instability and setting up Okoye's potential role. The scene doesn't stall the plot; it advances the succession subplot and reinforces the threat. However, it's a quieter scene in a sequence of action, so it may feel like a dip in energy.
“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 does make the reader want to keep reading, primarily because of the reveal of the Queen's death and the question of what Ross will do next. The scene ends with Ross walking back inside, which creates a sense of anticipation—what will he tell his superiors? The scene is effective in creating a hook, but it could be stronger if the ending was more ambiguous or surprising.
Up to this point, the script has been building momentum through the conflict with Namor and the political intrigue. This scene adds a new layer by revealing the Queen's death and setting up Ross's role in the coming conflict. The scene maintains the momentum, but it doesn't accelerate it significantly. The reader is likely to continue, but the scene feels like a necessary beat rather than a turning 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.
The scene ends on a strong hook: Shuri's decision to become the Black Panther and start immediately. This creates a clear sense of forward momentum and makes the reader want to see what happens next. The CIA office scene also leaves a thread dangling, as Val's decision to side with Ross is not fully resolved, and the threat of 'destabilization' remains. The scene effectively compels the reader to continue.
Up to this point in the script, the narrative has been building steadily, with the political conflict and the personal stakes converging. This scene is a key turning point, as it sets up Shuri's transformation into the Black Panther and the final confrontation with Namor. The script's momentum is strong, and this scene maintains that momentum by advancing both the plot and the character arc.
“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 creates some curiosity—will Shuri succeed in recreating the herb? Will Okoye fight?—but it doesn't create a strong sense of urgency. The montage format is efficient but not gripping. The reader is interested in the outcome, but not compelled to turn the page.
The scene is a necessary setup for the film's climax, but it doesn't add significant momentum. It confirms Shuri's plan and introduces the Midnight Angels, but it doesn't raise the stakes or introduce a new complication. The reader is ready to move on, but not excited to.
“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 hook—the herb glows, and Shuri is about to undergo the transformation. The reader is compelled to continue to see what happens next, especially with the promise of the Ancestral Plane. The emotional stakes also make the reader invested in Shuri's journey.
Up to this point, the script has built significant momentum through the conflict with Namor and Shuri's personal loss. This scene is a turning point—Shuri's decision to become the Black Panther—and it maintains the forward drive. The reader is invested in seeing how Shuri's transformation will play out.
“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 hook: Shuri's declaration of vengeance and Killmonger's 'We'll see...' leaves the reader eager to see if she follows through. The emotional and moral tension propels the reader forward.
This scene is a pivotal turning point in the script, and it maintains the momentum built over the previous scenes. Shuri's choice here will drive the climax, and the scene sets that up effectively. The script's overall momentum is strong, with this scene serving as a crucial beat.
“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 that makes the reader want to see what happens next—Shuri is now the Black Panther, and the stage is set for the confrontation with Namor. The arm-wrestle is a satisfying payoff. The scene compels the reader to continue to see how Shuri will use her new power.
Up to this point, the script has been building toward Shuri becoming the Black Panther. This scene delivers that payoff, and the momentum is strong. The reader is invested in Shuri's journey and wants to see her confront Namor. The scene maintains the script's momentum by providing a clear turning 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.
The scene ends with a strong hook: Shuri's declaration that they leave in the morning, and her exit. This creates anticipation for the battle to come. The debate also raises questions about whether M'Baku will join the fight, which makes us want to keep reading. What costs is that the scene is a bit static, and the hook could be stronger if there was a more immediate sense of danger or urgency.
Up to this point, the script has built strong momentum: Shuri has lost her mother, taken the herb, and become the Black Panther. This scene is a turning point where she commits to a plan to kill Namor. The scene maintains momentum by setting up the final battle. What costs is that the scene is a bit of a lull after the action of the previous scenes, and the debate could feel like a pause in the momentum. However, the scene's ending re-engages the reader by setting up the next action sequence.
“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 the reader to continue because it sets up a major battle and leaves Shuri's emotional state unresolved. The ambush setup creates anticipation, and the emotional conflict between Shuri and Nakia makes the reader want to see how Shuri's choice plays out. The scene ends with the ambush beginning, which is a strong hook.
The script's momentum is strong at this point. The scene builds on the previous scenes' setup and moves the plot forward toward the climactic battle. The emotional arc of Shuri's vengeance is a key thread that has been building, and this scene reinforces it. The script is clearly heading toward a major confrontation, and the momentum is maintained.
“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 does compel the reader to keep reading—the battle is escalating, and the reader wants to see how the Wakandans respond. However, the compulsion is based on the overall plot, not on anything specific to this scene. The scene itself doesn't create a hook or a question that makes the reader eager to turn the page.
The scene maintains the script's momentum. It's a short, efficient beat in a larger action sequence, and it keeps the plot moving forward. The reader is invested in the outcome of the battle, and this scene contributes to that investment by escalating the conflict. The momentum is strong, though it relies on the surrounding context.
“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 hook: Namor is captured, but the ship is losing speed, and Shuri is in a tense confrontation. The reader is compelled to continue to see how the capture plays out and what happens next.
The scene maintains the script's momentum, building on the previous action and setting up the next confrontation. The capture of Namor is a major turning point, and the scene delivers on the promise of the conflict.
“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—the RSL listing vertically in rough seas—which compels the reader to continue to see how the Wakandans survive. The whale attack is a surprising escalation that raises the stakes. The scene is effective at creating forward momentum.
Up to this point, the script has built momentum through the escalating conflict with Namor and the Talocanil. This scene maintains that momentum by showing a major setback for the Wakandans, which raises the stakes for the climax. The reader is invested in seeing how Shuri and the others will recover.
“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—the thruster explosion—that makes the reader want to know what happens next. The dual-front action and the arrival of the Midnight Angels also create anticipation. The scene is compelling and keeps the reader engaged, though the outcome of the duel is somewhat predictable.
Up to this point, the script has built significant momentum through the escalating conflict with Namor, the loss of Ramonda, and Shuri's transformation into the Black Panther. This scene maintains that momentum by raising the stakes and setting up the final confrontation. The reader is invested in Shuri's arc and wants to see how she resolves her vengeance vs. protection dilemma.
“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's high-stakes action and the cliffhanger of Shuri's kinetic explosion compel the reader to continue. The intercutting with the ocean battle adds urgency. The reader wants to know if Shuri will defeat Namor and if the Wakandans will survive. The 'OMITTED' sections are a minor distraction but don't diminish the pull.
Up to this point, the script has built strong momentum through the escalating conflict with Namor and the personal stakes of Shuri's grief. This scene maintains that momentum by delivering a satisfying physical confrontation and advancing the battle. The reader is invested in the outcome and the larger narrative arc.
“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, which is a strong hook. The reader wants to know if she catches him and what happens next. The deck battle also leaves questions about the outcome.
Up to this point, the script has built strong momentum through the escalating conflict. This scene maintains that momentum, pushing toward the climax. The reader is invested in the outcome of Shuri's quest for vengeance.
“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 is compelling and makes the reader want to continue. The resolution of the conflict is satisfying, but the final threat about Namor losing his throne creates a new thread of tension. The cut to the battle on the Royal Sea Leopard and the 'Wakanda Forever' chant provides a sense of closure, but the reader is left wondering about the future of this uneasy alliance. The scene is a strong climax, and the reader is invested in seeing how the story resolves.
The scene maintains strong script momentum. It resolves the central conflict of the film (Shuri vs. Namor) while setting up new threads (the alliance, the threat of Namor losing his throne, the ongoing battle). The scene is a turning point, and the reader is eager to see how the story continues. The momentum is strong, though the scene's predictability slightly reduces the sense of forward motion.
“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 hook: the transport van is stopped by a fallen tree, and the officers get out, setting up the rescue. The reader is compelled to continue to see how Ross is saved and what happens next. The scene's tension and cliffhanger are effective.
Up to this point, the script has built momentum through the Wakanda-Talocan conflict, Shuri's arc, and the political intrigue. This scene maintains that momentum by raising the stakes for Ross and setting up his rescue, which will likely tie into the larger plot. The scene doesn't stall the narrative; it advances it.
“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 is a quick, action-packed beat that makes us want to see what happens next—specifically, what Okoye and Ross will do now. However, the scene is so brief and the stakes are so underdeveloped that the compulsion to keep reading is moderate. We're curious, but not deeply invested.
The scene contributes to the overall momentum of the script by resolving Ross's immediate predicament and setting up his next move. It's a functional beat in the larger narrative, and it maintains the pace of the story. The scene doesn't derail the momentum, but it also doesn't significantly accelerate it.
“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 is a denouement, so the compulsion to keep reading is naturally lower. However, the scene doesn't offer any hook or question that makes the reader want to see what's next. The final beat with Riri is a smile, not a cliffhanger. The scene is satisfying but not compelling.
The script as a whole has strong momentum from the previous action scenes, and this denouement scene provides a necessary breather. It doesn't add much forward momentum, but it doesn't hurt it either. The scene is a calm before the final scene, which is appropriate.
“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 does not create a strong pull to keep reading. It resolves quickly and without tension, so the reader has little reason to turn the page. The lack of conflict or a cliffhanger makes it feel like a pause rather than a propulsive moment. The reader might be curious about what happens next, but the scene itself doesn't generate that curiosity.
The scene contributes to the overall script momentum by establishing M'Baku's rise, but it does so without adding dramatic tension. The script has been building toward this political shift, and the scene delivers it, but in a way that feels like a checkbox rather than a climax. The momentum is maintained but not accelerated.
“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's reveal of Toussaint is a strong hook that makes the reader want to see the next scene (the flashback and the final vision). The emotional payoff is satisfying, and the scene ends on a note of hope. However, the slow middle section might lose some readers, and the scene's predictability reduces the compulsion to keep reading.
This scene is a coda that resolves Shuri's arc, and it does so effectively. The reveal of Toussaint is a major payoff that recontextualizes the entire story, and the scene's emotional resolution is satisfying. The scene doesn't advance the plot, but it advances the character, which is appropriate for a finale. The momentum is maintained by the emotional stakes and the reveal.
“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.
As the final scene, the reader is not compelled to keep reading in the traditional sense, but the scene provides a satisfying conclusion that makes the reader want to revisit the script. The reveal is a strong hook, but since it's the end, the 'compelled to keep reading' is less relevant.
The scene provides a strong emotional conclusion that gives the script a sense of closure and thematic completion. It doesn't add new plot momentum, but it reinforces the script's emotional arc, making the whole feel more cohesive.
| 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.
Prices exclude VAT/sales tax, which is added at checkout based on your billing address where applicable.
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 on a powerful emotional beat that makes the reader want to continue. The death of T'Challa is a major event, and the reader is compelled to see how Shuri and Wakanda will cope. The scene also sets up the film's central conflict (grief and legacy). The only minor note is that the scene is a prologue, so the reader knows the story will continue, but the emotional hook is strong.
This scene establishes the emotional and narrative foundation for the entire script. It sets up Shuri's grief, her relationship with her mother, and the loss of the Black Panther. The momentum is strong because the reader wants to see how Shuri will evolve from this point. The scene also introduces key elements (the Heart-Shaped Herb, the lab, Griot) that will be important later. The script momentum is high.
No lens is broken, but Design, Execution and Involvement 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 is emotionally resonant and sets up Shuri's arc, but it doesn't create a strong pull to the next scene. The global reactions provide a sense of closure, and the scene ends on a somber note. The reader is likely to continue for the story's sake, but the scene itself doesn't end on a cliffhanger or a question that demands an answer.
Up to this point, the script has established T'Challa's death and Shuri's grief. The funeral scene reinforces the emotional stakes but doesn't advance the plot significantly. The momentum is carried by the emotional weight and the promise of future conflict (the UN hearing, the vibranium detector). The scene is a necessary beat but not a driver of 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 compels the reader to continue by establishing a clear conflict and hinting at larger threats. Ramonda's line about 'whispers' that 'Now is our time to strike' creates anticipation for how Wakanda will respond. The Mali intercut adds a sense of immediate danger. The scene ends on a strong note, making the reader want to see what happens next.
Up to this point, the script has established T'Challa's death, the funeral, and now the political pressure on Wakanda. This scene adds a new layer of conflict and sets up the threat of external forces. The momentum is building, with the Mali intercut hinting at covert operations. The scene contributes to the overall narrative momentum by raising the stakes and introducing the theme of Wakanda's vulnerability.
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 strong hook: the cargo ship and the vibranium detector, which promises a new threat. The reader is compelled to keep reading to see what happens next. The scene's combination of action and political intrigue maintains interest.
The scene builds on the previous scenes' momentum, showing Wakanda's proactive response to the threats established earlier. It also introduces a new plot thread (the cargo ship) that will likely lead to the next conflict. The script's momentum is maintained, though the scene doesn't dramatically escalate the stakes beyond what's already been established.
No lens is broken, but Design, Execution and Involvement 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—the blue-skinned woman on the boat deck—which compels the reader to continue. The deaths of the divers create a sense of danger that makes the reader want to know what happens next. The scene effectively raises questions: Who are these people? What do they want? The reader is invested in the mystery.
This scene contributes to the script's momentum by introducing a new threat and raising the stakes. It follows the previous scene's setup (the mining operation) and leads into the next scene (the attack on the boat). The scene is a turning point that shifts the plot from discovery to conflict. However, the momentum is somewhat generic—it's a standard 'horror set piece' that doesn't yet connect to the larger themes of the script (grief, legacy).
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 strong cliffhanger: the sirens breach again and start to sing a new melody, and Dr. Graham is escaping in the helicopter. This creates a strong pull to the next scene, where we expect to see Namor. The scene's escalating action and the mystery of the Talocanil make the reader want to continue.
Up to this point, the script has established the Talocanil threat and the global stakes. This scene advances the plot by showing the Talocanil's power and the humans' vulnerability, setting up the conflict with Wakanda. The momentum is strong, though the scene is more of a set piece than a character-driven beat. The script's overall momentum is maintained by the escalating action and the promise of Namor's reveal.
No lens is broken, but Design, Execution and Involvement 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 compels the reader to continue: the helicopter's destruction is a shocking event, and the newscaster's report about the UN and the succession creates intrigue. The reader wants to know how Wakanda will respond to this new threat. The scene effectively sets up the next conflict.
Up to this point, the script has established the threat of Namor and the Talocanil, and this scene escalates that threat by showing their power. The momentum is strong, with the action and political intrigue building. The scene maintains the script's forward drive, though the newscaster's exposition momentarily pauses the action.
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 makes the reader want to continue because it deepens our understanding of Shuri's emotional state and sets up the next scene (the drive and the ritual). The emotional stakes are high, and the reader is invested in Shuri's journey. However, the scene itself is not a page-turner; it's a character moment that builds anticipation for what comes next.
Up to this point, the script has established Shuri's grief and her avoidance, and this scene reinforces that while also introducing the possibility of healing. The scene contributes to the overall momentum by setting up the ritual that will be central to Shuri's arc. It doesn't advance the plot significantly, but it deepens the character, which is essential for the emotional payoff later.
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 strong emotional note that makes the reader want to see what happens next, especially with the impending arrival of Namor. The emotional depth of the scene creates investment in Shuri's journey. The scene is compelling, though the slow pacing in the middle might cause some readers to lose momentum. Overall, it effectively compels the reader to continue.
Up to this point, the script has established Shuri's grief and her resistance to healing, which is a strong foundation for her arc. This scene deepens that foundation and sets up the conflict with Namor. The script's momentum is steady, with a clear emotional throughline. The scene contributes to the overall narrative by advancing Shuri's character development, which is essential for the story's emotional stakes.
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.
The scene ends on a strong hook: the VB detector appearing by the fire, dripping with water, is a visual and narrative cliffhanger. The reader is compelled to keep reading to find out what it means, how they will respond, and what Namor's next move will be. The scene's momentum is strong.
Up to this point, the script has established a strong emotional foundation (T'Challa's death, Shuri's grief) and a growing external threat (the UN, the mining ship, the Talocanil). This scene escalates the threat by introducing Namor directly, and the momentum is maintained. The script is building towards a major conflict, and this scene is a key turning point. The momentum is strong.
No lens is broken, but Design and Involvement 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 is moderately compelling. The reader wants to know what the council decides, but the scene doesn't create a strong pull to keep reading. The debate is predictable, and the ending—Ramonda considering—is a soft cliffhanger. The reader is likely to continue but not with a strong sense of urgency or anticipation.
The scene maintains the script's momentum. It's a necessary beat in the story, setting up the central conflict and the council's response. It doesn't stall the plot, but it also doesn't accelerate it. The scene is a functional bridge between the discovery of Namor and the next action beat. The reader is likely to continue, but the scene doesn't create a strong sense of forward motion.
No lens is broken, but Design and Involvement 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.
The scene ends with a setup for the next scene (Ross's jog), but it doesn't create a strong pull. The decision to go is made, but the reader isn't desperate to see what happens next. The scene lacks a hook—a question, a threat, or an emotional cliffhanger.
The scene advances the plot—it sets up the mission to find the scientist—and maintains the script's momentum. However, it doesn't add much emotional or thematic momentum. The scene is a functional bridge, but it could do more to deepen Shuri's arc and the central conflict with Namor.
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 on a strong hook—Riri's 'WHAT?!' after learning about the merman—which makes the reader want to see what happens next. However, the middle of the scene is less compelling, and the reader might lose some momentum during the Ross conversation. The scene does its job of setting up the next conflict, but it doesn't create a burning desire to turn the page.
Up to this point, the script has been building momentum through the introduction of Namor, the attack on the cargo ship, and the political tension. This scene advances the plot by introducing Riri and setting up the next conflict. It maintains the script's momentum, though it's a quieter scene compared to the action that came before. The reader is likely to keep reading to see how the confrontation with Namor unfolds.
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 strong cliffhanger: the Kimoyo bead attaches to the armored car, setting up the escape. The reader is compelled to continue to see how they get out. The tension is high, and the scene's resolution is deferred, creating anticipation.
Up to this point, the script has built momentum through the introduction of Namor, the threat to Wakanda, and the mission to find Riri. This scene advances the plot by bringing the characters together and setting up the escape, which will lead to the confrontation with Namor. 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
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.
The scene ends on a strong action beat—the Barracuda crashing through the garage door—and the intercuts with the armored car create a sense of momentum. The reader is compelled to keep reading to see if they escape and what happens next with the police and Namor.
Up to this point, the script has built momentum through the escalating threat of Namor and the mission to protect Riri. This scene maintains that momentum with a fun, action-packed escape that also advances the characters' relationships. The reader is invested in seeing how the escape plays out and what happens next.
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 on a strong cliffhanger—Okoye's 'Shuri, where are you?'—which makes the reader want to continue to see if they reunite. The action is engaging and the intercutting creates a sense of urgency. The scene is a page-turner, even if it's a standard chase.
Up to this point, the script has built momentum through the chase and the introduction of Riri. This scene maintains that momentum, but it doesn't significantly advance the plot—it's a set piece. The reader is compelled to keep reading because of the action and the cliffhanger, but the scene doesn't introduce new information or raise the stakes beyond the immediate escape. The momentum is steady, not escalating.
No lens is broken, but Design, Execution and Involvement 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.
The scene is compelling. The chase is exciting, and the cutaway to Riri taking out the drone creates a satisfying payoff. The scene ends on a cliffhanger (Shuri warning Riri about the oxygen), which makes the reader want to continue to see if Riri succeeds. The scene is a strong page-turner.
The scene contributes to the script's momentum by advancing the escape sequence and setting up the next scene (Riri's suit and the drone). It maintains the fast pace of the action and keeps the plot moving. The scene is a solid part of the larger chase sequence, and it builds on the tension established in previous scenes.
No lens is broken, but Design, Execution and Involvement 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.
The scene is engaging enough to keep reading, but it doesn't create a strong pull to the next page. The action is resolved, and the next beat (the blockade) is set up, but there's no cliffhanger or emotional hook. The reader is likely to continue because of the overall story, not this scene alone.
Up to this point, the script has built momentum through the chase sequence, and this scene maintains that momentum. The action is consistent with the previous scenes, and the stakes are clear. The scene doesn't stall the narrative; it propels it forward toward the next obstacle.
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 on a strong hook: Shuri is captured, Riri is about to be taken, and the reader wants to know what happens next. The action and stakes compel the reader to continue. The only slight dip is the middle fight, but the ending is effective.
Up to this point, the script has built momentum through the chase and the escalating threat of the Talocanil. This scene raises the stakes by capturing Shuri, which will drive the next act. The momentum is strong, and the reader is invested in the outcome.
No lens is broken, but Design and Involvement 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 does compel the reader to keep reading, mainly because of the unresolved tension: Ross has the bracelet, Val is suspicious, and the ride to the office promises more conflict. The scene ends on a note of anticipation. The reader wants to know what happens next, both in the immediate scene (the car ride) and in the larger plot (the investigation).
The scene maintains the script's momentum by advancing the plot (the US investigation) and setting up future conflicts (Ross's ride with Val, the search for Shuri). It also raises the stakes for the characters. The scene is a necessary beat in the larger narrative, and it does its job of keeping the story moving.
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 strong hook: Okoye is stripped of her rank, and Ramonda is left grieving. The reader is compelled to continue to see how Okoye will react and what will happen to Shuri. The transition to the lab scene, where Ramonda discovers Shuri's recording, adds another layer of intrigue.
This scene is a pivotal moment in the script, raising the stakes for Okoye and deepening Ramonda's grief. It maintains the script's momentum by setting up Okoye's potential redemption arc and the ongoing search for Shuri. The scene's emotional weight carries forward, making the reader invested in the characters' fates.
No lens is broken, but Design and Involvement 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 doesn't create a strong pull to keep reading. The tension is brief, and the resolution is too neat. The Ramonda call is a letdown—it's mostly exposition. The scene feels like a bridge, not a hook.
The scene advances the plot (Ross gets the beads, talks to Ramonda) but doesn't add significant momentum. It's a necessary scene but not a driving one. The script's overall momentum is strong, but this scene is a dip.
No lens is broken, but Design and Involvement 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 ends with a strong visual hook—Ramonda blowing the conch and throwing it into the ocean—which compels the reader to continue. However, the scene itself is not particularly gripping; the conversation is calm and informational. The hook is effective, but the scene could do more to build anticipation.
The scene advances the plot by establishing the alliance between Ramonda and Ross and setting up the laptop subplot. It also transitions to the beach scene, which is a new location and a new development. The momentum is steady but not strong; the scene is a necessary step but doesn't add significant urgency.
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 strong hook: Ramonda's prayer to Bast and her decision to seek Nakia's help. This creates anticipation for the next scene, as we wonder if Nakia can rescue Shuri in time. The scene's tension and the unresolved threat compel the reader to continue.
Up to this point, the script has built momentum through a series of escalating conflicts: the UN hearing, the attack on the cargo ship, the introduction of Namor, and now this direct confrontation. The scene advances the plot by setting up the rescue mission and raising the stakes for the upcoming conflict. The script's momentum is strong, with each scene leading logically to the next.
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 a strong hook: the Mayan Elder's warning about K'uk'ulkan and the danger of searching for him. This creates anticipation for the next scene, where Nakia will presumably find the beach and encounter Namor. The scene also leaves the reader wanting to know how Nakia will rescue Shuri. The scene is compelling and makes the reader want to continue.
The scene advances the plot by setting up Nakia's mission and introducing the Mayan Elder as a guide. It also deepens the emotional stakes and reinforces the threat of Namor. The scene maintains the script's momentum by moving from the personal (Ramonda's plea) to the mythic (the Elder's story), keeping the reader engaged. The script's overall momentum is strong, and this scene contributes to it.
No lens is broken, but Design and Involvement 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 does make the reader want to continue. The mystery of the cave, the threat of Namor, and the dynamic between Shuri and Riri are all compelling. The scene ends with Shuri being led to Namor, which is a strong hook. However, the scene could be more compelling if it ended on a more specific question or a moment of higher tension.
This scene is part of a larger narrative, and it does contribute to the momentum. It moves Shuri from captivity to a meeting with Namor, which is a key plot point. The scene also develops the Shuri-Riri relationship, which is important for the story. However, the scene doesn't add much new information or raise the stakes significantly; it's more of a transition scene. The momentum is maintained but not accelerated.
Design and Involvement 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 is compelling because of the content of the backstory. The audience wants to know how Namor became who he is. However, the scene itself does not create a strong pull to keep reading. The present-tense interaction is static, and the scene ends with the flashback, which is a natural stopping point. The scene does not end on a cliffhanger or a question that demands an answer. The audience is left with a sense of completion, not anticipation.
Up to this point, the script has been building momentum through action and political intrigue. This scene is a deliberate pause for exposition and character development. It is a necessary scene, but it does slow the momentum. The scene is a 'breather' in the narrative, and it is placed at a point where the audience is invested enough to tolerate a slower pace. The scene does not derail the momentum, but it does not add to it.
Involvement 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 compels the reader to continue because it deepens Namor's character and sets up his conflict with Wakanda. The friar's curse is a hook that makes us want to see how it plays out. The montage's brisk pace keeps the story moving, and the emotional beats make us care about Namor.
Up to this point, the script has established Shuri's grief, the threat of Namor, and the political tensions. This backstory scene adds depth to Namor, making him a more sympathetic antagonist. It maintains the script's momentum by explaining his motivations, which will pay off in the final confrontation. The scene doesn't stall the plot; it enriches it.
No lens is broken, but Design and Involvement 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 creates some curiosity about Talocan, but it doesn't create a strong compulsion to keep reading. The negotiation is resolved, and the scene ends with a setup for the underwater city, which is a visual spectacle but not a dramatic cliffhanger. The audience might want to see Talocan, but the emotional stakes are low. The scene doesn't end with a question or a threat that makes the reader eager to turn the page.
Up to this point, the script has built momentum through the conflict with Namor, the abduction of Shuri and Riri, and the threat to Wakanda. This scene continues that momentum by setting up the alliance and the tour of Talocan, which is a key worldbuilding moment. The scene doesn't stall the plot; it advances the relationship between Shuri and Namor, which is central to the story. The momentum is maintained, though not significantly increased.
No lens is broken, but Involvement 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 is beautiful but not gripping. The tour structure and lack of conflict make it easy to put down. The offer at the end ('Nothing') is a mild hook, but it doesn't create a strong desire to know what happens next. The reader might be curious about the Sastun project, but the scene doesn't end on a cliffhanger or a question.
Up to this point, the script has built momentum through action and political intrigue. This scene is a breather, a worldbuilding pause. It doesn't advance the plot much, but it deepens Namor's character and sets up the Sastun project, which will be important later. The momentum is maintained by the promise of future conflict, but this scene itself is a lull.
No lens is broken, but Design and Involvement 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.
The scene ends on a cliffhanger ('Off the guard’s look...') which is a classic hook, but the hook is weak because the guard's look is generic. The reader is mildly curious but not desperate to know what happens next. The scene's brevity and lack of tension reduce its pull.
The scene advances the plot: it sets up the infiltration mission that will lead to the laptop's destruction. It's a necessary step in the larger narrative, and the reader is invested in the overall story. The scene's brevity keeps the momentum moving, even if the scene itself is not a standout.
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 is competent and moves the plot forward, but it doesn't create a strong desire to keep reading. The mission is successful, but the lack of tension or emotional stakes makes it feel like a checkbox. The reader is likely to continue because of the larger plot, not because of this scene's hook.
The scene contributes to the overall momentum of the script by advancing the subplot of destroying the laptop and protecting Wakanda. It's a necessary step in the larger narrative. The scene doesn't stall the plot, but it also doesn't add significant momentum on its own. The reader is likely to continue because of the main storyline, not this scene.
Involvement 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 creates some forward momentum—the audience wants to know if Shuri's plan will work and if Nakia will rescue her. But the scene's middle section is flat, and the intercut with Nakia feels like a separate scene. The ending ('Let us watch the sastun rise') is a hook, but it's not a strong one. The scene doesn't make the reader desperate to turn the page.
The scene contributes to the script's momentum by advancing the plot—Shuri's plan is set in motion, and Nakia's rescue is underway. But the scene doesn't add much emotional or thematic momentum. It's a functional step in the story, not a turning point. The script's overall momentum is strong, but this scene is a lull.
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.
The scene ends with a strong hook: Namor's threat to verify Ramonda's claim and the implication that he will attack. The B134 block raises the stakes and leaves the reader wanting to know what happens next. The scene is compelling, but the middle section (A134) could be more gripping. Overall, the scene does its job of propelling the reader forward.
Up to this point, the script has built a complex conflict with multiple factions. This scene advances the plot by solidifying Namor's threat and setting up the attack on Wakanda. The momentum is strong, but the scene's dialogue-heavy middle could slow the reader's engagement. The script's overall momentum is maintained by the high stakes and the emotional arc.
No lens is broken, but Execution and Involvement 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.
The scene ends with a clear hook—the escape is underway, and the audience wants to know if they'll make it. The rescue is a satisfying turn, but the scene doesn't create a strong desire to see what happens next beyond the immediate action.
The scene maintains the script's momentum by moving the plot forward—Shuri and Riri are rescued, and the story can progress. The scene doesn't stall, but it also doesn't add significant new information or character development. It's a functional bridge scene.
No lens is broken, but Design, Execution and Involvement 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.
The scene does compel the reader to continue, mainly because of the unresolved threads: Okoye's demotion, Namor's inevitable retaliation, and Shuri's determination to get to her lab. The scene ends with a clear forward motion ('I need to get to my lab'), which hints at the next step. However, the scene itself is not a page-turner; it's a calm moment that relies on the audience's investment in the characters.
The script's momentum is strong overall. This scene is a necessary beat in the larger narrative, and it maintains the forward drive by resolving the rescue and setting up the next conflict. The scene doesn't stall the plot; it moves it forward. The momentum is carried by the unresolved threads and the audience's investment in Shuri's arc.
No lens is broken, but Design, Execution and Involvement 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.
The scene compels the reader to continue because it sets up a major conflict and raises the stakes. The reader wants to see how Wakanda will respond to Namor's threat. The scene is a strong turning point, though it's not the most gripping scene in the script—it's more of a setup than a cliffhanger. The reader is invested in the outcome.
Up to this point, the script has built momentum through Shuri's capture, escape, and the escalating threat of Namor. This scene solidifies the antagonist's resolve and sets the stage for the climactic battle. The script's momentum is strong, and this scene maintains it by raising the stakes and moving the plot forward. The reader is eager to see the confrontation.
No lens is broken, but Design, Execution and Involvement 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.
The scene ends with a Siren sighting, which is a hook, but the preceding beats are low-energy. The reader is mildly curious about the Siren but not compelled by the characters' emotional states. The scene feels like a pause rather than a turning point.
Up to this point, the script has built momentum through action and political intrigue. This scene is a necessary breather, but it doesn't add much momentum. It confirms Shuri's safety and sets up the next attack, but the emotional beats are underdeveloped.
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 ends with a strong hook: 'We're under attack.' This compels the reader to continue to see how the characters respond. The emotional investment in Okoye and Nakia also makes the reader want to see them survive. The scene is effective in driving the narrative forward.
This scene is a turning point in the script, moving from character development to the major action set piece. It maintains the script's momentum by setting up the attack on Wakanda. The scene is effective in transitioning the narrative into the climax.
No lens is broken, but Design, Execution and Involvement 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.
The scene ends with a strong hook: Ramonda and Riri are now piloting the rescue fleet, and the attack is escalating. The reader wants to know if they can save the city and what happens to Shuri. The scene compels the reader to continue.
Up to this point, the script has built momentum through the escalating conflict with Namor and the personal stakes for Shuri and Ramonda. This scene continues that momentum, raising the stakes and setting up the next phase of the attack. The script is compelling and the reader is invested in the outcome.
Involvement 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.
The scene ends with Talon Fighters raining fire on Talocanil warriors, which is a strong action beat that makes the reader want to see the outcome. The appearance of Namor walking toward the palace creates anticipation for a confrontation. The scene's fast pace and high stakes keep the reader engaged. However, the scene is part of a longer battle, so the compulsion to keep reading is more about the overall battle than this specific scene's cliffhanger.
The scene contributes to the script's momentum by escalating the attack and moving Namor closer to the palace. The battle is a major turning point in the story, and this scene shows the scale of the threat. The momentum is strong, but it's part of a longer sequence, so the scene itself doesn't provide a major shift in the story's direction. The momentum is maintained by the action and the clear progression toward a confrontation.
No lens is broken, but Design, Execution and Involvement 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.
The scene ends on a strong cliffhanger: Namor's spear cracks the glass but holds, and Griot announces one minute until the last scarab beetle is safe. The reader is compelled to continue to see if the glass breaks and what happens to Ramonda and Riri. The action is engaging and the stakes are high.
Up to this point, the script has built momentum through the attack on Wakanda, and this scene escalates it further. The reader is invested in the outcome of the battle and the fate of the royal family. The scene maintains the script's momentum by raising the stakes and setting up the next confrontation.
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.
The scene ends on a powerful cliffhanger: the Queen is dead, and Namor has issued an ultimatum. The reader is compelled to continue to see how Shuri will respond and whether Wakanda will fall. The emotional stakes are so high that it's impossible not to want to know what happens next.
Up to this point, the script has built momentum through escalating conflicts and emotional stakes. This scene is a major turning point that propels the narrative into its final act. The death of the Queen raises the stakes for Shuri's transformation into the Black Panther, and the reader is invested in seeing how she will avenge her mother. The script's momentum is strong, and this scene is a key driver.
No lens is broken, but Involvement 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's emotional intensity and the question of whether Shuri will survive compel the reader to continue. The resolution—Shuri choosing to live—creates a natural curiosity about what she will do next. The scene ends on a note of tentative hope, but the reader is aware that the larger conflict with Namor is unresolved, which drives momentum.
Up to this point, the script has been building toward Shuri's lowest point. This scene is a crucial turning point in her arc, moving her from passive grief to a potential active role. The scene's resolution—Shuri choosing to live—sets up her transformation into the Black Panther. The momentum is strong, as the reader is invested in Shuri's journey and eager to see how she will confront Namor.
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 is emotionally compelling, but it doesn't create a strong pull to keep reading. The conversation is self-contained, and the ending—M'Baku walking away—feels like a natural pause. The transition to the hydrobomb discovery provides a new plot thread, but it's a separate scene. The scene could be more compelling if it ended on a more active or intriguing note, such as Shuri making a decision that has immediate consequences.
The scene contributes to the script's momentum by solidifying Shuri's motivation and setting up the next phase of the plot (the evacuation and the hydrobomb). The scene is a necessary beat in Shuri's arc, moving her from grief to a thirst for vengeance. The script's momentum is maintained, though this scene is more of a character beat than a plot driver.
No lens is broken, but Design, Execution and Involvement 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 Okoye considering the offer, which is a decent hook. However, the council scene is slow, and the reader might lose interest before reaching the more compelling Okoye scene. The scene doesn't end on a strong cliffhanger—it's a thoughtful pause.
Up to this point, the script has been building toward the confrontation with Namor. This scene maintains that momentum by showing the political instability and setting up Okoye's potential role. The scene doesn't stall the plot; it advances the succession subplot and reinforces the threat. However, it's a quieter scene in a sequence of action, so it may feel like a dip in energy.
No lens is broken, but Design and Involvement 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 does make the reader want to keep reading, primarily because of the reveal of the Queen's death and the question of what Ross will do next. The scene ends with Ross walking back inside, which creates a sense of anticipation—what will he tell his superiors? The scene is effective in creating a hook, but it could be stronger if the ending was more ambiguous or surprising.
Up to this point, the script has been building momentum through the conflict with Namor and the political intrigue. This scene adds a new layer by revealing the Queen's death and setting up Ross's role in the coming conflict. The scene maintains the momentum, but it doesn't accelerate it significantly. The reader is likely to continue, but the scene feels like a necessary beat rather than a turning point.
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 on a strong hook: Shuri's decision to become the Black Panther and start immediately. This creates a clear sense of forward momentum and makes the reader want to see what happens next. The CIA office scene also leaves a thread dangling, as Val's decision to side with Ross is not fully resolved, and the threat of 'destabilization' remains. The scene effectively compels the reader to continue.
Up to this point in the script, the narrative has been building steadily, with the political conflict and the personal stakes converging. This scene is a key turning point, as it sets up Shuri's transformation into the Black Panther and the final confrontation with Namor. The script's momentum is strong, and this scene maintains that momentum by advancing both the plot and the character arc.
No lens is broken, but Design, Execution and Involvement 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 creates some curiosity—will Shuri succeed in recreating the herb? Will Okoye fight?—but it doesn't create a strong sense of urgency. The montage format is efficient but not gripping. The reader is interested in the outcome, but not compelled to turn the page.
The scene is a necessary setup for the film's climax, but it doesn't add significant momentum. It confirms Shuri's plan and introduces the Midnight Angels, but it doesn't raise the stakes or introduce a new complication. The reader is ready to move on, but not excited to.
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 on a strong hook—the herb glows, and Shuri is about to undergo the transformation. The reader is compelled to continue to see what happens next, especially with the promise of the Ancestral Plane. The emotional stakes also make the reader invested in Shuri's journey.
Up to this point, the script has built significant momentum through the conflict with Namor and Shuri's personal loss. This scene is a turning point—Shuri's decision to become the Black Panther—and it maintains the forward drive. The reader is invested in seeing how Shuri's transformation will play out.
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 on a strong hook: Shuri's declaration of vengeance and Killmonger's 'We'll see...' leaves the reader eager to see if she follows through. The emotional and moral tension propels the reader forward.
This scene is a pivotal turning point in the script, and it maintains the momentum built over the previous scenes. Shuri's choice here will drive the climax, and the scene sets that up effectively. The script's overall momentum is strong, with this scene serving as a crucial beat.
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 that makes the reader want to see what happens next—Shuri is now the Black Panther, and the stage is set for the confrontation with Namor. The arm-wrestle is a satisfying payoff. The scene compels the reader to continue to see how Shuri will use her new power.
Up to this point, the script has been building toward Shuri becoming the Black Panther. This scene delivers that payoff, and the momentum is strong. The reader is invested in Shuri's journey and wants to see her confront Namor. The scene maintains the script's momentum by providing a clear turning point.
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 a strong hook: Shuri's declaration that they leave in the morning, and her exit. This creates anticipation for the battle to come. The debate also raises questions about whether M'Baku will join the fight, which makes us want to keep reading. What costs is that the scene is a bit static, and the hook could be stronger if there was a more immediate sense of danger or urgency.
Up to this point, the script has built strong momentum: Shuri has lost her mother, taken the herb, and become the Black Panther. This scene is a turning point where she commits to a plan to kill Namor. The scene maintains momentum by setting up the final battle. What costs is that the scene is a bit of a lull after the action of the previous scenes, and the debate could feel like a pause in the momentum. However, the scene's ending re-engages the reader by setting up the next action sequence.
No lens is broken, but Design, Execution and Involvement 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.
The scene compels the reader to continue because it sets up a major battle and leaves Shuri's emotional state unresolved. The ambush setup creates anticipation, and the emotional conflict between Shuri and Nakia makes the reader want to see how Shuri's choice plays out. The scene ends with the ambush beginning, which is a strong hook.
The script's momentum is strong at this point. The scene builds on the previous scenes' setup and moves the plot forward toward the climactic battle. The emotional arc of Shuri's vengeance is a key thread that has been building, and this scene reinforces it. The script is clearly heading toward a major confrontation, and the momentum is maintained.
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.
The scene does compel the reader to keep reading—the battle is escalating, and the reader wants to see how the Wakandans respond. However, the compulsion is based on the overall plot, not on anything specific to this scene. The scene itself doesn't create a hook or a question that makes the reader eager to turn the page.
The scene maintains the script's momentum. It's a short, efficient beat in a larger action sequence, and it keeps the plot moving forward. The reader is invested in the outcome of the battle, and this scene contributes to that investment by escalating the conflict. The momentum is strong, though it relies on the surrounding context.
No lens is broken, but Design, Execution and Involvement 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 on a strong hook: Namor is captured, but the ship is losing speed, and Shuri is in a tense confrontation. The reader is compelled to continue to see how the capture plays out and what happens next.
The scene maintains the script's momentum, building on the previous action and setting up the next confrontation. The capture of Namor is a major turning point, and the scene delivers on the promise of the conflict.
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.
The scene ends on a strong cliffhanger—the RSL listing vertically in rough seas—which compels the reader to continue to see how the Wakandans survive. The whale attack is a surprising escalation that raises the stakes. The scene is effective at creating forward momentum.
Up to this point, the script has built momentum through the escalating conflict with Namor and the Talocanil. This scene maintains that momentum by showing a major setback for the Wakandans, which raises the stakes for the climax. The reader is invested in seeing how Shuri and the others will recover.
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.
The scene ends on a strong cliffhanger—the thruster explosion—that makes the reader want to know what happens next. The dual-front action and the arrival of the Midnight Angels also create anticipation. The scene is compelling and keeps the reader engaged, though the outcome of the duel is somewhat predictable.
Up to this point, the script has built significant momentum through the escalating conflict with Namor, the loss of Ramonda, and Shuri's transformation into the Black Panther. This scene maintains that momentum by raising the stakes and setting up the final confrontation. The reader is invested in Shuri's arc and wants to see how she resolves her vengeance vs. protection dilemma.
No lens is broken, but Design, Execution and Involvement 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's high-stakes action and the cliffhanger of Shuri's kinetic explosion compel the reader to continue. The intercutting with the ocean battle adds urgency. The reader wants to know if Shuri will defeat Namor and if the Wakandans will survive. The 'OMITTED' sections are a minor distraction but don't diminish the pull.
Up to this point, the script has built strong momentum through the escalating conflict with Namor and the personal stakes of Shuri's grief. This scene maintains that momentum by delivering a satisfying physical confrontation and advancing the battle. The reader is invested in the outcome and the larger narrative arc.
No lens is broken, but Design, Execution and Involvement 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, which is a strong hook. The reader wants to know if she catches him and what happens next. The deck battle also leaves questions about the outcome.
Up to this point, the script has built strong momentum through the escalating conflict. This scene maintains that momentum, pushing toward the climax. The reader is invested in the outcome of Shuri's quest for vengeance.
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 is compelling and makes the reader want to continue. The resolution of the conflict is satisfying, but the final threat about Namor losing his throne creates a new thread of tension. The cut to the battle on the Royal Sea Leopard and the 'Wakanda Forever' chant provides a sense of closure, but the reader is left wondering about the future of this uneasy alliance. The scene is a strong climax, and the reader is invested in seeing how the story resolves.
The scene maintains strong script momentum. It resolves the central conflict of the film (Shuri vs. Namor) while setting up new threads (the alliance, the threat of Namor losing his throne, the ongoing battle). The scene is a turning point, and the reader is eager to see how the story continues. The momentum is strong, though the scene's predictability slightly reduces the sense of forward motion.
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 on a strong hook: the transport van is stopped by a fallen tree, and the officers get out, setting up the rescue. The reader is compelled to continue to see how Ross is saved and what happens next. The scene's tension and cliffhanger are effective.
Up to this point, the script has built momentum through the Wakanda-Talocan conflict, Shuri's arc, and the political intrigue. This scene maintains that momentum by raising the stakes for Ross and setting up his rescue, which will likely tie into the larger plot. The scene doesn't stall the narrative; it advances it.
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 is a quick, action-packed beat that makes us want to see what happens next—specifically, what Okoye and Ross will do now. However, the scene is so brief and the stakes are so underdeveloped that the compulsion to keep reading is moderate. We're curious, but not deeply invested.
The scene contributes to the overall momentum of the script by resolving Ross's immediate predicament and setting up his next move. It's a functional beat in the larger narrative, and it maintains the pace of the story. The scene doesn't derail the momentum, but it also doesn't significantly accelerate it.
No lens is broken, but Design and Involvement 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.
The scene is a denouement, so the compulsion to keep reading is naturally lower. However, the scene doesn't offer any hook or question that makes the reader want to see what's next. The final beat with Riri is a smile, not a cliffhanger. The scene is satisfying but not compelling.
The script as a whole has strong momentum from the previous action scenes, and this denouement scene provides a necessary breather. It doesn't add much forward momentum, but it doesn't hurt it either. The scene is a calm before the final scene, which is appropriate.
No lens is broken, but Design and Involvement 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 does not create a strong pull to keep reading. It resolves quickly and without tension, so the reader has little reason to turn the page. The lack of conflict or a cliffhanger makes it feel like a pause rather than a propulsive moment. The reader might be curious about what happens next, but the scene itself doesn't generate that curiosity.
The scene contributes to the overall script momentum by establishing M'Baku's rise, but it does so without adding dramatic tension. The script has been building toward this political shift, and the scene delivers it, but in a way that feels like a checkbox rather than a climax. The momentum is maintained but not accelerated.
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's reveal of Toussaint is a strong hook that makes the reader want to see the next scene (the flashback and the final vision). The emotional payoff is satisfying, and the scene ends on a note of hope. However, the slow middle section might lose some readers, and the scene's predictability reduces the compulsion to keep reading.
This scene is a coda that resolves Shuri's arc, and it does so effectively. The reveal of Toussaint is a major payoff that recontextualizes the entire story, and the scene's emotional resolution is satisfying. The scene doesn't advance the plot, but it advances the character, which is appropriate for a finale. The momentum is maintained by the emotional stakes and the reveal.
No lens is broken, but Design and Involvement 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.
As the final scene, the reader is not compelled to keep reading in the traditional sense, but the scene provides a satisfying conclusion that makes the reader want to revisit the script. The reveal is a strong hook, but since it's the end, the 'compelled to keep reading' is less relevant.
The scene provides a strong emotional conclusion that gives the script a sense of closure and thematic completion. It doesn't add new plot momentum, but it reinforces the script's emotional arc, making the whole feel more cohesive.
The screenplay delivers a deeply emotional and thematically rich character journey, anchored by Shuri's transformation from a grief-stricken princess into a vengeful yet ultimately merciful Black Panther. Namor is a standout antagonist, given a tragic backstory that makes his threat feel justified and his eventual alliance earned. Supporting characters like Okoye and Nakia receive meaningful arcs, though several secondary figures—particularly M'Baku, Namora, and the tribal elders—remain underdeveloped. The script's greatest strength is its willingness to let grief drive character decisions, creating a resonant and human core beneath the superhero spectacle.
Character development in this screenplay is driven by loss and the search for purpose. Shuri's arc is the emotional spine: she moves through denial, rage, a dark night of the soul, and finally a choice to break the cycle of vengeance—mirroring the film's central theme that grief can either consume or transform. Namor is a rare antagonist who is both a formidable threat and a sympathetic figure; his colonial trauma and love for his people make his actions comprehensible, and his surrender feels like a genuine character shift rather than a plot convenience. Okoye's fall from grace and redemption as a Midnight Angel provides a compelling parallel to Shuri, while Nakia's secret son recontextualizes T'Challa's legacy and gives Shuri a future to protect. However, the screenplay spreads its focus thin in places: M'Baku's political maneuvering and challenge for the throne feel abrupt, Namora's loyalty shift is underexplored, and Riri's arc, while charming, follows a predictable 'reluctant hero finds courage' template. The tribal elders function mostly as exposition devices. Overall, the screenplay achieves profound emotional impact through its central characters, but would benefit from deepening its supporting cast to match the richness of its leads.
The screenplay establishes a genuinely moving and culturally specific premise—a grieving Wakanda confronted by an underwater Mayan superpower—and uses it to power a resonant coming-of-rage arc for Shuri. The foundational idea is clear and emotionally engaging, but the premise is somewhat weakened by a slow geopolitical front-load, a familiar hidden-kingdom antagonist structure, and an overstuffed middle act that delays the central confrontation.
Black Panther: Wakanda Forever begins with a powerful real-world elegy and builds a conflict that is both intimate and epic: grief renders Wakanda vulnerable just as Namor's hidden Talocan emerges from the ocean. The premise successfully fuses franchise obligations (introducing Ironheart, honoring T'Challa) with a thematic inquiry into vengeance, legacy, and what a protector owes her people. It has strong emotional hooks and offers a morally gray antagonist whose backstory gives the conflict depth. However, the premise's clarity suffers from Namor's oscillating demands, and its originality is limited by structural similarities to other Marvel and underwater-kingdom films. Still, the premise's emotional foundation and its surprising final hope—T'Challa's son—give it considerable audience appeal.
The screenplay possesses a strong emotional core, anchored by Shuri's grief-driven arc, a devastating midpoint turn, and a thematically resonant finale. The structure, however, sags in the middle—particularly in the extended Boston chase and the Talocan interludes—and struggles to fully clarify Namor's shifting motivations. The Wakanda attack and Killmonger Ancestral Plane sequence are standout dramatic moments. Overall, the narrative is ambitious and emotionally effective, but pacing and plot coherence in the second act would benefit from tightening.
The story is constructed as a grief-to-redemption epic, following Shuri from the loss of her brother through the murder of her mother to her eventual choice to spare Namor and embrace hope. The three-act structure is recognizable: a prologue establishing loss, a middle act of pursuit and captivity in Talocan, and a climactic war leading to reconciliation. While the emotional architecture is effective, the narrative occasionally loses momentum in the middle, and certain plot developments (the reintroduction of a vibranium detector, Namor's alliance ultimatum) arrive with insufficient setup. The screenplay is nonetheless a coherent and compelling sequel that uses its structure to serve character and theme, even when the plot mechanics creak.
The screenplay effectively centers its thematic exploration around grief, vengeance versus mercy, and the legacy of loss, achieving an emotionally coherent and strong narrative arc. It successfully connects Shuri's personal transformation to larger themes of leadership, nationhood, and breaking cycles of violence, though it sometimes states its themes explicitly rather than letting them emerge organically. The bold choice to have Shuri spare Namor and the final reveal of T'Challa's son provide emotional and thematic closure, deepening the resonance of the story. However, the thematic treatment could be more novel in spots, and the role of tradition versus innovation deserves a sharper resolution.
The screenplay revisits the central thematic tensions of its predecessor—isolationism versus globalism, tradition versus progress, and identity shaped by loss—but grounds them in Shuri's intimate, trauma-driven journey. The narrative integrates the grief motif with political conflict in a way that transforms an external war with Talocan into a reflection of Shuri's internal war with rage and hopelessness. The themes are clear and consistent, with a particularly memorable exploration of ancestral connection and the psychological weight of failure. The treatment of vengeance is the anchor: Shuri's arc leads to a deliberate departure from Killmonger's path, concluding with a mercy that reframes the meaning of Wakandan leadership. While occasionally the message is delivered through direct dialogue, the progression is compelling and the resolution with the white funeral garments being burned feels earned and symbolic. The screenplay also braids in timely notions of colonization and resource extraction without losing its emotional center, though it could deepen some of these ideas through action rather than exposition.
Black Panther: Wakanda Forever's screenplay presents a visually ambitious and emotionally grounded sequel that uses spectacle in service of grief. The imagery is strongest when it fuses personal ritual with mythic scale—the levitating funeral casket, the bioluminescent Talocan, the flooded throne room—and weakest in generic action shorthand and conventional government-thriller backdrops. The visual language of water, fire, and mourning clothes is deployed with sophistication, creating a rich foundation for a director and production designer to build upon.
The screenplay's visual imagination is exemplary in its world-building and emotional set pieces. Talocan's underwater civilization is a creative triumph, with kelp-based fiber optics, glowing Sastuns, and the Weber Azul plant transforming the ocean floor into a new mythology. Wakanda's design continues to shine through ceremonies, rites, and the functional elegance of kimoyo bead technology. At the same time, several extended action sequences lean on generic descriptors ('balletic combat,' 'coordinated moves'), the middle act's spy-machinations look visually interchangeable with any CIA thriller, and the flood attack could exploit Wakandan-specific landmarks more powerfully. Improving image specificity in action beats and deepening the visual contrast between realms would elevate the screenplay further.
The screenplay delivers a powerful emotional journey centered on grief, legacy, and the burden of leadership. Shuri's arc from rage to reluctant mercy is the emotional backbone, supported by culturally rich mourning rituals and a cathartic final reveal. However, some emotional beats—particularly Ramonda's death, Okoye's dismissal, and Riri's integration—are underdeveloped or rushed, preventing the story from achieving its full resonant potential.
Black Panther: Wakanda Forever is emotionally ambitious, using loss as its engine. The film's greatest strength is its unflinching portrayal of grief, especially through Shuri, whose anger and vulnerability feel authentic. The funeral sequences, mother-daughter dynamics, and the final legacy reveal create moments of genuine poignancy. Yet the screenplay sometimes prioritizes plot mechanics over emotional continuity, leaving secondary characters with incomplete arcs and undercutting the impact of major deaths. The emotional core is strong, but the execution is uneven.
The screenplay establishes a clear and emotionally charged central conflict between Wakanda and Namor, anchored by Shuri's grief and evolution. The stakes are high—national survival, personal vengeance, and the fate of two hidden civilizations—but several supporting threads, particularly the U.S. political subplot and Shuri's final psychological turn, are underdeveloped. Strong action and character-driven tension make the narrative engaging, though causal connections and the cost of resolution could be tightened.
The conflict is rooted in character: Wakanda must protect itself without T'Challa, while Shuri must transform grief into leadership. Namor serves as a compelling mirror, his own generational trauma motivating his aggression. The screenplay escalates from political pressure to covert infiltration to a devastating full-scale attack, culminating in a desert duel that resolves Shuri's internal battle. However, the middle act occasionally gets lost in procedural thriller elements, and the final turn toward mercy would benefit from a more explicit psychological payoff.
This screenplay delivers a culturally rich and emotionally grounded sequel that expands the Wakandan mythos into an underwater Mesoamerican civilization. Its greatest creative assets are the vivid world-building of Talocan, the subversion of Shuri's ancestral-plane confrontation, and a final reveal that re-centers the story on legacy and hope. While the broad three-act structure hews to familiar superhero conventions, the script consistently freshens familiar tropes with cultural specificity, thematic weight, and character-driven choices.
The screenplay is a confident, inventive follow-up that uses grief as its engine and cultural collision as its fuel. The introduction of Namor and the Talocanil—rooted in Mayan and Aztec iconography rather than standard Atlantean clichés—is a bold and refreshing creative move. Shuri's arc from rage to reluctant mercy, and her unexpected ancestral encounter with Killmonger, provide genuine narrative surprises. The script's weaknesses lie in its occasionally formulaic plot mechanics: the 'enemy captured, hero ascends, final battle' sequence is recognizable, and Namor's 'my people first' motivation overlaps with Killmonger's earlier arc. Still, the screenplay's thematic ambition, enriched representation, and emotionally resonant ending mark it as a distinctly creative entry in the genre.
A masterful blockbuster sequel that expertly balances profound thematic inquiry into grief and colonialism with high-octane franchise spectacle.
A mainstream commercial blockbuster that bets heavily on a 'prestige' emotional core centered on grief and the weight of legacy.
Overview — what it's like to read this script right now
The script delivers a somber, epic, and tonally rich reading experience that distinguishes itself from standard genre fare through its commitment to character-driven drama. It is most effective when exploring Shuri’s internal struggle between scientific rationalism and the spiritual weight of her heritage, creating a compelling causal link between her grief and her eventual ascension. While the read is propulsive, it occasionally strains under its own length, particularly where the CIA political subplot diverges from the more visceral Shuri-Namor conflict. The script successfully fulfills its ambitious contract by providing a resonant tribute to its predecessor while expanding the world-building with the distinct, culturally specific introduction of Talocan.
Protect & Amplify (2) — what's working and should be preserved
Issues (3) — what's affecting the read and why
Evidence
Revision Paths — different ways to address this
Evidence
Revision Paths — different ways to address this
Evidence
Revision Paths — different ways to address this
Credibility Flags (1) — polish signals a professional reader notices; usually quick wins
Evidence
Decision Anatomy — advocacy, verdict stability, revision posture
Main advocacy asset
The script’s bold thematic subversion—specifically Shuri's encounter with Killmonger in the Ancestral Plane—elevates it from a standard sequel to a profound character study.
Main advocacy blocker
The overall length and the slightly repetitive 'capture/rescue' logic in the second act occasionally dampen the narrative momentum.
Why not lower
The script is written with such high technical proficiency and emotional intelligence that it clearly sits above the 'Consider' band.
Why not higher
The excessive length and the occasionally clunky integration of franchise-maintenance subplots (Val/Ross) prevent it from being a 'flawless' 10.
Read trajectory
The script opens with immense emotional power and closes with a satisfyingly epic finale, but the middle section gets bogged down in logistics and subplots.
Authorial signature
The writers' voices are consistently present in the soulful handling of Wakandan culture and the nuanced portrayal of Namor's anti-colonialist rage.
Revision leverage
Tighten the Cambridge chase and Ross/Val subplot to focus more intensely on the Shuri/Namor ideological conflict.
Revision depth
The script's foundation is rock-solid; it simply requires a surgical tightening of the second act to reach peak efficiency.
Ask Gemini about this read
A propulsive superhero sequel that delivers spectacle and emotional weight on grief while expanding its world with clear commercial framing.
A mainstream_commercial superhero action film with elevated_commercial thematic ambitions around grief, legacy, and global power, delivering spectacle and emotional resonance under franchise constraints.
Overview — what it's like to read this script right now
The script reads as a high-stakes action drama that maintains momentum through its set pieces and world expansion into Talocan. It is strongest when the personal stakes of Shuri's grief intersect with the larger political conflict, generating layered tension across multiple fronts. The read strains in the second act where the multiple fronts of the conflict begin to fragment focus and slow causal accumulation. The script is reaching for a balance between franchise expectations and thematic resonance on legacy and loss, and largely achieves it in the action sequences while the emotional core lands with varying intensity.
Protect & Amplify (2) — what's working and should be preserved
Issues (4) — what's affecting the read and why
Evidence
Revision Paths — different ways to address this
Evidence
Revision Paths — different ways to address this
Evidence
Revision Paths — different ways to address this
Evidence
Revision Paths — different ways to address this
Decision Anatomy — advocacy, verdict stability, revision posture
Main advocacy asset
The Talocan world-building through cultural specificity gives the script a distinctive asset that would survive skeptical coverage discussion.
Main advocacy blocker
The unclear desire after the funeral sequences creates a structural drag that would require acknowledgment in any advocacy case.
Read trajectory
The first act establishes grief and threat with clear momentum; the second act fragments across multiple threads; the third act regains propulsion through the desert climax and resolution.
Authorial signature
The integration of cultural specificity into action set pieces creates a coherent voice that distinguishes this from generic franchise entries.
Revision leverage
Re-clarify Shuri's post-funeral desire in action around scene 46 so the middle act accumulates causal pressure rather than running parallel threads.
Revision depth
The desire clarification is act-structural; without it the middle sequences remain additive rather than escalating, so line-level revision cannot recover the read.
Ask Grok about this read
A vivid, emotionally ambitious franchise adventure whose second-act sprawl and compressed climax keep its strongest character work from fully coalescing.
A mainstream commercial superhero adventure aiming to combine large-scale action and franchise worldbuilding with an emotionally grounded story about grief, cultural memory, and choosing protection over vengeance.
Overview — what it's like to read this script right now
The script reads as a large-scale superhero adventure that pairs kinetic action and irreverent exchanges with a sustained register of grief, cultural memory, and political threat. Its strongest engagement comes when spectacle is tied to intimate emotional material, giving the action a human cost rather than making it an end in itself. The read becomes less cohesive through the middle stretch, where the expanding world and operational plot repeatedly redirect attention from the central emotional journey. The draft reaches for both broad, propulsive entertainment and a meaningful account of mourning and restraint; it delivers memorable moments of both, but not always a continuous dramatic build between them.
Protect & Amplify (2) — what's working and should be preserved
Issues (3) — what's affecting the read and why
Evidence
Revision Paths — different ways to address this
Evidence
Revision Paths — different ways to address this
Evidence
Revision Paths — different ways to address this
Credibility Flags (2) — polish signals a professional reader notices; usually quick wins
Decision Anatomy — advocacy, verdict stability, revision posture
Main advocacy asset
The grief-and-ritual thread gives the spectacle a clear emotional center and provides a specific, memorable case for the script beyond its action mechanics.
Main advocacy blocker
The second act’s sequence of new plot modules and worldbuilding makes the central character journey less continuous than the film’s emotional ambition requires.
Why not lower
The script has a coherent emotional center, distinctive cultural worldbuilding, and several action sequences that clearly affect the characters and their communities.
Why not higher
The middle stretch diffuses the main dramatic line, while Shuri’s climactic turn and the terms of the resolution arrive with less dramatized development than their importance warrants.
Read trajectory
The opening establishes grief, political pressure, and a vivid new threat, but the middle disperses attention across plot and worldbuilding, and the final action is stronger than the dramatic articulation of its resolution.
Authorial signature
The combination of Wakandan ritual, Talokan’s visual-cultural specificity, familial grief, and brisk humor gives the script a recognizable identity within its superhero action framework.
Revision leverage
Rebuild the second-act sequence chain around how each encounter changes Shuri’s relationship to grief, Talokan, and the choice between vengeance and protection.
Revision depth
The core premise and three-act shape are intact, but the middle-act connective tissue and the final character resolution need focused restructuring rather than line polish alone.
Ask OpenAI about this read
A tonally confident franchise continuation with strong emotional anchors and vivid world-building that loses causal and emotional focus as its subplots and set pieces multiply.
A mainstream franchise sequel aiming for spectacle and grief-driven emotional stakes, with its primary bet on a legible ensemble throughline inside a large-scale conflict.
Overview — what it's like to read this script right now
The script reads as a large-scale, emotionally grounded franchise sequel that moves between mourning, political intrigue, and spectacle with a consistent confidence in its own world. Its strongest reading experience comes from its opening movement and from the moments where grief, family, and cultural ritual carry weight alongside action. The read strains through its middle and late stretches, where the number of active storylines and the rapid turns in several characters' goals make it harder to track what each character is pursuing and why. The gap between what the script reaches for, a grief story that becomes a larger reckoning, and what the current draft consistently delivers is narrowest in its early and mid sections.
Protect & Amplify (2) — what's working and should be preserved
Issues (4) — what's affecting the read and why
Evidence
Revision Paths — different ways to address this
Evidence
Revision Paths — different ways to address this
Evidence
Revision Paths — different ways to address this
Evidence
Revision Paths — different ways to address this
Credibility Flags (2) — polish signals a professional reader notices; usually quick wins
Decision Anatomy — advocacy, verdict stability, revision posture
Main advocacy asset
The Talocan world-building gives the script an antagonist whose motives are rooted in a specific cultural and colonial history, which a reader can champion as distinctive material. This asset is represented directly by the protect_amplify item for Talocan's grounded civilization.
Main advocacy blocker
The fragmentation of the central throughline across parallel storylines makes it hard for a reader to see the script as one accumulating story. This is the blocker most likely to draw skeptical pushback in a coverage discussion.
Why not lower
The script's grief-driven opening, its distinct antagonist world, and the Riri material give it enough assets to support a Consider call despite its structural strain.
Why not higher
The subplot fragmentation and the unstable antagonist motive are both act-level problems that would need structural revision before the script could read as a Recommend.
Read trajectory
The opening establishes grief and ritual with clarity, but the middle act's proliferating threads and shifting antagonist motive weaken the read before the third act's spectacle partially recovers it.
Authorial signature
The script's cultural specificity, its dialogue rhythm for Riri and the Dora, and its ritual-based structure give it a recognizable voice across most sequences.
Revision leverage
Consolidate the parallel storylines around one shared objective for the second act so that each cut advances the same hunt and the same threat.
Revision depth
The fragmentation and the antagonist's shifting motive are act-level causal problems, so line or scene revisions alone cannot restore the read's forward pull.
Ask Claude about this read
A propulsive, well-executed Marvel tentpole that delivers on spectacle and emotional stakes but is held back by a crowded ensemble, a mid-section that sags under worldbuilding, and a protagonist whose interiority arrives late.
A mainstream commercial superhero epic aiming for emotional resonance through grief, ritual, and the cost of leadership, with a primary craft bet on spectacle and worldbuilding.
Overview — what it's like to read this script right now
The script reads as a confident, large-scale superhero epic that moves with real momentum and delivers several genuinely rousing set-pieces. It is strongest when it leans into grief, ritual, and the emotional cost of loss — the opening funeral sequence and the mother-daughter scenes carry real weight. The read strains in the middle, where the introduction of Talocan and its mythology slows the forward pull, and in the back half, where the ensemble grows so large that individual arcs compete for space. The script is reaching for a blockbuster that earns its emotional beats, and it largely succeeds — the gap between ambition and execution is narrowest in the first act and widest in the middle stretch.
Protect & Amplify (2) — what's working and should be preserved
Issues (4) — what's affecting the read and why
Evidence
Revision Paths — different ways to address this
Evidence
Revision Paths — different ways to address this
Evidence
Revision Paths — different ways to address this
Evidence
Revision Paths — different ways to address this
Credibility Flags (2) — polish signals a professional reader notices; usually quick wins
Decision Anatomy — advocacy, verdict stability, revision posture
Main advocacy asset
The script's handling of grief and ritual gives it a genuine emotional core that elevates it above standard superhero fare, and the funeral sequence and riverbank scenes are strong enough to anchor a coverage discussion.
Main advocacy blocker
The middle act's sag under worldbuilding is the primary obstacle to advocacy, as it slows the read and dilutes the forward momentum that makes the first act so effective.
Why not lower
The script's emotional core and strong first act prevent it from falling into Pass territory, as the grief-driven sequences are genuinely effective and the set-pieces are well-executed.
Why not higher
The middle act's pacing issues and the protagonist's late-arriving interiority keep it from reaching Recommend, as these problems materially affect the read experience.
Read trajectory
The first act is emotionally grounded and propulsive, the middle act sags under worldbuilding and exposition, and the third act recovers with strong set-pieces but rushes some character resolutions.
Authorial signature
The script has moments of distinctive voice — particularly in the ritual scenes and the ancestral plane sequence — but the action sequences and dialogue often read as generic for the genre.
Revision leverage
Tighten the middle act by intercutting the Talocan sequences with the Wakandan response, maintaining forward pressure while preserving the worldbuilding.
Revision depth
The issues are concentrated in the middle act and the protagonist's arc, requiring targeted rewrites rather than a foundational rethink of the premise or structure.
Ask DeepSeek about this read
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