D&D 5e Scenario Builder
For the encounters that are not fights: a negotiation, a chase, getting in unseen, a room that wants the party dead, a trail of clues, a test of skill, a journey running out of water. Write one up so another DM can run it cold, and share it to the gallery beside the fights.
Writing a scenario someone else can run
A fight answers itself: here are the monsters, roll initiative. Nothing in this tool does. A negotiation is answered by what the other side wants; a chase by how much of a lead there is; an investigation by what can be found and where. That is why the form changes with the kind you pick — it opens the questions that kind is really about.
Always say how it ends
The one thing required for every kind is what counts as winning. A fight can assume "defeat them". A negotiation, a heist or a chase has no obvious ending, and a DM running it cold needs to know what the table is aiming for before the first sentence.
Say what losing looks like, too
It is rarely "they die". The quarry gets away, the alarm is raised, the deal goes to someone else. Deciding it now saves the moment at the table where everyone looks at you.
Stat blocks are optional
Most of these are won without anyone rolling initiative. If someone in the cast might end up in a fight, say what they fight like and the builder links the real stat block — from the SRD or the community gallery — rather than copying numbers into the scenario.
Clues need places
A clue with nowhere to find it is one the table only gets if the DM decides to hand it over. Write down where each one is, and consider more than one route to the conclusion that matters.