We Were Five: Workshopping to Storyform to Storyweaving

A full Narrova workflow that moves from Workshopping to Storyforming to Storyweaving, including GPT-5.2 Deliberate/Detailed Storyforming and a reconciled Storyform for downstream use.

Type: ExampleWorkflow: Workshopping -> Storyforming -> Storyweaving Output: Storyform Last updated: September 6, 2025

Want a full Narrova workflow that moves from open-ended ideation to a locked Storyform and a finished treatment? Here is the exact sequence, plus the prompts that drive each pass.

TL;DR

  1. Workshop multiple horror premises until one concept has heat.
  2. Refine the chosen idea with tighter variations and a logline.
  3. Draft the Four Throughlines to verify the Storymind.
  4. Storyform the narrative with Deliberate + Detailed settings.
  5. Validate alignment, then sketch Signposts and Drivers.
  6. Storyweave into a treatment that tracks OS/MC/IC/RS in parallel.
  7. Workshop titles once the narrative identity is clear.

I worked with a mixture of Agents: Workshopping in the beginning to get some ideas flowing, then Storyforming to narrow down the context and intent of the story, and then Storyweaving to put it all together.

Storyforming was hooked up to GPT-5.2. For the pass when I asked it to go ahead and figure the whole Storyform, I set Narrova to Deliberate thinking and Detailed response length. While there were some inconsistencies during the process (mis-aligned and incompatible parts), the final Storyform it landed on and saved into context was 100% accurate.

We are very encouraged by these new updates, and look forward to integrating them into the Dramatica platform as we work to make it the very best tool for modern story development.

Story Development with Narrova

The following is a sample conversation with Narrova, the multi-agentic narrative intelligence that sits at the heart of the Dramatica platform.

Before we share the conversation, a quick note on what you are about to see and how it was produced.

This story was developed with Narrova in three primary passes, in a deliberate progression from possibility to structure to execution: Workshopping, then Storyforming, then Storyweaving. Workshopping was used twice–first at the beginning to expand the initial idea into viable directions (premise, characters, thematic angles), and again at the end to generate and refine potential story titles once the narrative identity was clear.

Once we had enough raw material, we moved into the Storyforming pass to identify and formalize the complete Storyform that would govern the story’s underlying narrative logic. For that Storyforming pass, we explicitly set Narrova to Deliberate thinking with a Detailed response length, and we were very pleased with the Storyform it arrived at.

As with any automated or semi-automated Storyform synthesis, there were a few minor inconsistencies in the raw output–some elements that would be incompatible in a fully aligned Dramatica Storyform if taken literally side-by-side. However, Narrova resolved those contradictions when saving the Storyform for downstream use, selecting the coherent set of choices and normalizing the record so subsequent passes could build on a stable foundation. We will continue tightening this over time, but we also view this as a feature, not a flaw: story development is inherently iterative. Early drafts benefit from allowing contradictions to coexist long enough to be tested, challenged, and refined–until the narrative converges on the final, fully aligned Storyform that the treatment (and ultimately the script) can confidently express.

Step-by-step workflow (with the Jim prompts)

  1. Workshop premises (wide net).

    Jim asks: “Workshop some story ideas about four friends hiking. Stephen king style”

    Narrova responds with: multiple premise directions you can quickly compare for tone, hook, and structure.

    The four friends follow a little-known trail that does not appear on any map, only to realize it is slowly rearranging itself behind them–trees, rocks, even the sky shifting–like the forest is editing reality, and it seems especially interested in the most broken of the four.

    The rest of the response continues with several distinct premise variations, each built around a different hook, letting you compare tone, stakes, and structural potential before committing.

  2. Narrow the direction by iteration.

    Jim asks: “More like the 3rd one” (repeated to tighten the concept)

    Narrova responds with: variations around the selected premise, keeping the spine but shifting the flavor.

    One friend ducks into the trees to pee, steps over a gnarled root that looks weirdly like a hand, and vanishes for a breath; when he stumbles back, grinning and confused, the others realize his watch is on the wrong wrist, his favorite hiking joke is different, and he swears a trail landmark they have not passed yet is “just behind them.”

    The remaining bullets keep the same core premise but shift the pressure, adding thresholds, memory swaps, and identity bleed so you can feel which version best supports the Throughlines.

  3. Lock the concept in a logline.

    Jim asks: “Oh the glitching bodies one is interesting. Let’s do a logline for it”

    Narrova responds with: a crisp logline that reveals the core conflict and stakes.

    On a remote mountain trail, four friends lose one of their own for a single, impossible second–when he returns, his body and memories begin to “glitch,” subtly changing every time they cross a natural boundary in the wilderness, while the others feel pieces of their identities vanishing, forcing them to confront the terrifying possibility that the forest is collapsing multiple versions of their lives into his unstable, ever-shifting form.

    The rest of the response tightens the core conflict into a Storyform-ready anchor so later choices stay aligned with the same stakes.

  4. Validate the Storymind with Throughlines.

    Jim asks: “Use the original idea that they used to be a group of five and write out the Four Throughlines”

    Narrova responds with: OS, MC, IC, and RS Throughlines to ensure the story holds together.

    Overall Story (OS) Throughline – “The Hike That Eats People.” All four friends are trapped in a remote forest where reality is unstable: the trail loops, landmarks shift, and their group history keeps rewriting itself.

    The rest of the response spells out MC, IC, and RS Throughlines tied to the “we were five” fracture, confirming the Storymind balance before Storyforming.

  5. Storyform pass (Deliberate + Detailed).

    Jim asks: “Let’s go ahead and nail down the Storyform for this one.”

    Narrova responds with: Domains + Concerns, then Issues, Problems/Solutions, and full Story Dynamics.

    Here is a clean Dramatica-friendly setup for your glitching-hike story using the “we used to be five” idea.

    The response then lays out Domains, Concerns, Issues, Problems/Solutions, and Story Dynamics to lock the structural engine before Signposts and Storyweaving.

  6. Tune the MC psychology before final alignment.

    Jim asks: “Make the MC in Psychology totally something we haven’t talked about yet.”

    Narrova responds with: several baggage options, then locks the chosen one into the Storyform.

    The Story-Spinner (Concern leans toward Conceptualizing)… Friends joke that they are the “screenwriter” of the group. On the trail, when reality starts editing them, they lose the privilege of being the one who controls the story.

    The rest of the response offers multiple baggage options and maps how each shifts the MC Concern while staying in Psychology.

  7. Confirm alignment, then sketch Signposts.

    Jim asks: “Review the saved Storyform… Sketches the IC and RS now too.”

    Narrova responds with: Signpost sketches for OS/MC/IC/RS and a consistency check.

    Within that frame, the OS Signposts move: Past… Progress… Future… Present… In parallel, the MC Signposts go: Conceptualizing… Being… Becoming… Conceiving…

    The response sketches OS/MC/IC/RS progressions so you can see how Throughlines advance in parallel before Drivers.

  8. Clarify constraints, then map Drivers.

    Jim asks: “The IC should never reach their Solution. Work out the five major story drivers now.”

    Narrova responds with: a five-driver spine that stays Action-driven and honors the constraint.

    Five Major Story Drivers (all Actions that force Decisions).

    The rest of the response lists the five Drivers with their forced Decisions, keeping the Action spine while honoring the IC never-Solution constraint.

  9. Storyweave into a treatment.

    Jim asks: “Now draft the treatment maintaining all the detail.”

    Narrova responds with: a full treatment that tracks OS/MC/IC/RS and lands a Failure/Bad ending.

    Four old friends hike into an isolated mountain forest to reconnect… The story ends in Failure (they do not preserve the true Past) and Bad Judgment (the MC is wrecked).

    The remaining treatment tracks OS/MC/IC/RS across Acts I-III, landing the Failure/Bad experience while preserving the Storyform choices.

  10. Title pass (Workshopping again).

Jim asks: “Clever story titles?”

Narrova responds with: a short list of title options tuned to tone and theme.

We Were Five… The Fifth Was Here… Versions of Us.

The rest of the response explains each title’s tonal fit and how it reflects the Storymind once the Storyform is locked.

Conversation

Full transcript: We Were Five Story Development