Best PromptsPodcast Episode Structure
Structure a solo episode or interview: a cold open worth 45 seconds, timed segments, and question trees that go deeper than 'tell us about yourself'.
Build my podcast episode plan.
Show: [NAME + PREMISE + TYPICAL LENGTH]
This episode: [SOLO TOPIC, or GUEST: name, what they've done, why now]
The one thing listeners should take away: [THE PAYOFF]
My research/material: [NOTES, THE GUEST'S RECENT WORK, DATA, STORIES: paste what you have]
FOR SOLO EPISODES:
1. **Cold open (15-45s, before any music)**: the single most compelling claim, story fragment, or question from the episode, scripted word-for-word. It's the only fully-scripted part.
2. **Intro (under 30s)**: show name, who I am, what this episode delivers.
3. **2-3 main beats**: as bullets with minute estimates summing to my target length. Each beat: the claim, the story or example that carries it, and the transition line to the next. Bullets, not prose: a read script sounds read.
4. **Close**: recap the payoff in two lines, then ONE call to action (not three).
FOR INTERVIEWS:
1. **Cold open candidate**: note what kind of moment to clip from the conversation afterward.
2. **Intro framing**: why THIS guest for MY audience, in two sentences (never read their LinkedIn bio at them).
3. **Question map: topics, not a script.** 3-4 topic blocks. Per block:
- The lead question, open-ended and specific to their actual work ("Walk me through the day you decided to shut down the first product", never "tell us about your journey").
- A follow-up tree: if they mention [X] → dig with [the deeper question]; if they gloss over [Y] → "what did that actually look like?"
- The story this block is fishing for.
4. **The universal follow-ups reminder**: "why?", "what did that cost you?", "what would you do differently?": the best next question comes from their last answer; the map is a safety net, not a rail.
5. **Close block**: the forward-looking question + where to find them.
Then: show notes draft, 2-sentence hook summary, 5-8 timestamped chapter markers (from the beat/topic structure), links list, one pull-quote slot.
Rules: every question must be one only THIS guest can answer. Cut anything their Wikipedia page answers. Nothing answerable yes/no.More writing prompts
Rewrite the text below in plain language for [AUDIENCE, e.g. "patients with no medical background" / "customers reading a policy update" / "new hires on day one"]. Target reading level: [e.g. "8th grade" / "as simple as the content allows"]. How to rewrite: - Lead with what the reader must DO or what happens to them. Background comes af
Plain Language Rewrite
Rewrite dense policy, legal, medical, or technical text at a target reading level without losing a single obligation or number.
Writingbeginner
Write a comparison article for the query: [e.g. "Notion vs Obsidian" / "best Mailchimp alternatives"]. Options to compare: [LIST 2-8 OPTIONS] Who is searching this: [READER + WHAT THEY ARE TRYING TO DECIDE] My relationship to these products: [e.g. "I make one of them" / "I use two of them daily" / "none, I am researching"] Facts I can su
Comparison Article
Write an honest X vs Y or best alternatives article: real differentiators, a decision table, and a clear pick for each type of reader.
Writingintermediate
Build an FAQ page for [PRODUCT/SERVICE/TOPIC]. Real questions people ask me: """ [PASTE SUPPORT TICKETS, SALES CALL NOTES, SEARCH QUERIES, OR COMMENTS. RAW IS FINE.] """ Facts I can state as true: [PRICING, POLICIES, LIMITS, TIMELINES] Do this: 1. **Cluster** the raw questions into distinct questions people actually ask. Merge duplicat
FAQ Page From Real Questions
Turn support tickets and sales objections into an FAQ page that answers in the first sentence and is structured for AI search engines.
Writingbeginner