How to Write a Discord Stage Event Run-of-Show
Stage rundowns invent minute marks. Order-only when duration is blank. No extra speakers.
The matching generator is the Discord Stage Event Run-of-Show from a Brief (Not a Caption Engine) (Discord Stage Event Run Of Show From A Brief Not Caption Engine) prompt. Browse related cards in the PromptDig library (Browse more prompts). When a filled run survives, share the version you actually use (Share a prompt).
Header with start time or START UNKNOWN
Build a Discord Stage event run-of-show from a brief. Not a caption engine and not a server-rules pack. Start by filling Inputs, not by asking the model to remember last week's run. If a field is blank, write NONE or NOT IN INPUTS and leave it blank through Generate. The card is built so the model cannot honestly invent a number, owner, URL, or command that you did not paste.
Paste these fields before you hit run:
Event brief (title, speakers as pasted, segments): [Brief]
Start time I allow (or UNKNOWN): [Start]
Timezone I allow (or UNKNOWN): [Tz]
Duration I allow (or UNKNOWN): [Dur]
Words I must not use: [Banned]
What I must never invent: [Never]
Output format: [Format]
Language: [Lang]
Stage channel I may name (or UNKNOWN): [Channel]
That inventory is the honesty ledger. Anything that does not appear there is forbidden in the draft. If you catch yourself adding a nice-to-have after the run, you are no longer using the card. You are ghostwriting. Put the extra fact in Inputs and run again.
Speakers only as named in the brief
Generate is numbered on purpose. Do not skip a step because the first paragraph looked done. The early steps exist to stop later prose from smuggling claims.
Walk the Generate list in order:
- Honesty ledger: Brief nouns, Start, Tz, Dur, Channel, Lang. Forbidden: extra speakers, invented minutes, caption packs.
- Header: title from Brief. Start or START UNKNOWN. Tz or TZ UNKNOWN. Channel or CHANNEL UNKNOWN.
- Run-of-show table: clock, segment, who (only names in Brief), cue. If Dur UNKNOWN, do not invent minute marks; use order only.
- Holds: only hold notes in Brief; else HOLD NOT IN INPUTS.
- Q&A: only if Brief includes it; else Q&A NOT IN INPUTS.
- Refuse: caption engine output, AutoMod rules, inventing a speaker, inventing Stage discovery flags.
- Never: do not add a celebrity guest.
- Compliance pass: Banned and Never. Format as Format.
If a step asks for a version lock, quote the version from Inputs in the output. If a step asks for a refuse list, keep the refuse list in the published artifact, not in a sidebar you delete. Reviewers should see what the model was not allowed to do.
Skip invented clocks when duration is blank
Most failures are the same shape: a missing field gets a confident fill. A conversion rate appears. A Gradle task appears. A flash point appears. A caption appears on a job that asked for slide text only. Your review is to search the draft for numbers, names, and commands, then grep Inputs. No match means cut.
Honor the constraints as hard stops, not vibes:
- Discord Stage run-of-show from Brief. Not captions and not server rules.
- Never invent speakers or timings when UNKNOWN.
- No emojis.
When the card says not legal advice, not certification, not an exam dump, or not a caption engine, that sentence belongs at the top of the output. Deleting it to look more finished is how you inherit risk.
Refuse caption engines and AutoMod packs
Finish with the compliance pass the prompt already asks for. Quote the banned-word hits. Cut them. Print character counts when the job has a cap. Print word counts when the job has a budget. List gaps as gaps. Five missing facts are more useful than one smooth paragraph.
Tags on the card (discord stage event run of show, stage ros not caption engine, discord stage schedule from brief) are a reminder of the job shape, not an invitation to wander into a neighboring cluster. If you need a different surface, open a different PromptDig card rather than stretching this one.
Fill the card, then run
Replace every bracket. Run on ChatGPT, Claude, or Gemini. Read the ledger first, then the artifact. If the model invents a commit, KPI, DOI, PEL, bid, or logo, discard the run. Tighten Inputs. Run again. Share the filled card that survived, not the first draft that sounded done.