The newsletter prompt playbook
Most people write a fresh prompt every time they want AI to draft their newsletter, then spend five rounds fixing the output. A prompt playbook fixes that. It's a reusable set of instructions that tells AI exactly how to write your newsletter, so every issue starts from "use my playbook with this transcript" instead of a blank page. The full template is below, copy-paste ready.
What a prompt playbook is
A prompt playbook is a reusable set of instructions that tells AI exactly how to create a specific type of content. Instead of writing a new prompt every time, you use the same playbook and just swap in new source material.
Here's what that looks like in practice.
Without a playbook
Write new prompt → Explain format → Explain tone → Explain structure → Hope it works → Revise 5 times
With a playbook
"Use my newsletter playbook with this transcript" → Done
How to use this template
Four steps, and only the first one takes real effort:
- Customize the template. Fill in the [BRACKETED] sections with your specifics.
- Save it as your playbook. Name it
NEWSLETTER-PROMPT-PLAYBOOK.md. - Use it every time. Reference it whenever you want to create a newsletter.
- Iterate and improve. Update based on what works.
Get a new build-with-AI guide every week
Weekly playbooks on prompting, agents, and content systems — free.
You're in. First email lands shortly.
The full playbook
This is the whole thing. Copy it, fill in the brackets, and hand it to Claude or ChatGPT along with your transcript. It covers reference files, audience, structure, subject lines, tone, formatting, a quality checklist, and deliverables, so the model has nothing left to guess about.
# NEWSLETTER PROMPT PLAYBOOK
## From YouTube Transcript to Published Newsletter
---
## REFERENCE FILES
Before creating the newsletter, please read these files:
1. My Knowledge Base: [YOUR-KNOWLEDGE-BASE.md]
2. My Brand Voice Guide: [YOUR-BRAND-VOICE-GUIDE.md]
---
## SOURCE MATERIAL
I'm providing you with a [YouTube transcript / coaching call / video script] called:
[ATTACH YOUR TRANSCRIPT FILE]
---
## NEWSLETTER DETAILS
**Newsletter Name:** [Your newsletter name]
**Platform:** [Substack / ConvertKit / Beehiiv / etc.]
**Target Read Time:** [2-3 minutes / 3-5 minutes / 5-7 minutes]
**Target Word Count:** [500-750 / 750-1000 / 1000-1500] words
**Publish Day:** [Day of week]
---
## TARGET AUDIENCE
Write this newsletter for: [Describe your reader]
They care about: [What problems they want solved]
Their goal is to: [What transformation they want]
---
## NEWSLETTER STRUCTURE
Follow this structure:
### 1. HOOK (First 2-3 sentences)
- Open with a bold claim, counterintuitive insight, or relatable problem
- Make the reader think "I need to keep reading"
- Don't start with "Hey [name]" or generic greetings
### 2. THE PROBLEM/SETUP (1-2 paragraphs)
- Describe the challenge or situation
- Make the reader feel seen ("If you've ever...")
- Create tension that the rest of the newsletter will resolve
### 3. THE FRAMEWORK/SOLUTION (Main body)
- Introduce the key concept or framework from the transcript
- Break it down into clear, digestible parts
- Use examples from the transcript where relevant
- Label any framework components clearly
### 4. APPLICATION/ACTION STEPS (1-2 paragraphs)
- Tell the reader exactly how to apply this
- Make it specific and actionable
- "Try this in your next [situation]"
### 5. CLOSE (2-3 sentences)
- Recap the main insight
- End with a memorable line or callback to the hook
- Sign off with just your first name
---
## SUBJECT LINE REQUIREMENTS
Create 3 subject line options:
- Under 45 characters each
- Curiosity-driven or benefit-focused
- No clickbait - must accurately represent content
Format:
- Option 1: "[Subject]" (XX characters)
- Option 2: "[Subject]" (XX characters)
- Option 3: "[Subject]" (XX characters)
---
## TONE & STYLE REQUIREMENTS
### DO:
- Write like you're talking to a smart friend
- Use short sentences and short paragraphs
- Be direct - get to the point quickly
- Use "you" language (not "one should")
- Include specific examples
- Make it scannable with clear section breaks
### DON'T:
- Use corporate jargon ("leverage," "synergy," "utilize")
- Use AI clichés ("let's dive in," "game-changer," "in today's world")
- Use excessive exclamation points
- Be vague or theoretical
- Write paragraphs longer than 3-4 sentences
- Use em-dashes (—) excessively
---
## FORMATTING REQUIREMENTS
- Use ## for main section headers (sparingly)
- Use **bold** for key terms or emphasis (not entire sentences)
- Use bullet points for lists of 3+ items
- Leave blank lines between paragraphs
- No images or graphics (text only)
---
## CONTENT QUALITY CHECKLIST
Before finalizing, verify:
☐ **No fluff** - Every sentence adds value
☐ **No redundancy** - Don't repeat the same point in different words
☐ **Specific not vague** - Examples, numbers, details
☐ **Actionable** - Reader knows exactly what to do
☐ **Sounds like me** - Matches my voice guide
☐ **Under word count** - Tighter is better
---
## CALL TO ACTION (Optional)
If you want to include a CTA, add at the end:
**Option A - Soft CTA:**
"If you found this helpful, share it with someone who needs it."
**Option B - Product CTA:**
"If you want to go deeper on [topic], check out [product/resource]."
**Option C - Engagement CTA:**
"Reply and tell me: [question related to topic]"
---
## DELIVERABLES
Please provide:
1. **3 subject line options** (with character counts)
2. **The full newsletter** (formatted for [platform])
3. **A one-sentence summary** I can use for social promotion
---
## EXAMPLE OF WHAT GOOD OUTPUT LOOKS LIKE
[Paste an example of a newsletter you've written that represents your ideal output. This helps AI understand the target.]
---
END OF PLAYBOOK How to build your own playbook (the real way)
This template is a starting point. The REAL power comes from iterating. The playbook you end up with a few months from now should look different from the one above, because it will be built on your actual feedback instead of generic best practices.
The iteration-to-playbook process runs in rounds:
- Rounds 1–5. Create newsletters using a basic prompt. Save each conversation.
- Rounds 6–10. Notice what feedback you give repeatedly. Start adding those instructions to your prompt.
- Rounds 11–15. Your prompt is getting longer and more specific. You're giving less feedback.
- Rounds 16–20. The prompt is working well consistently. You rarely need to revise.
After 20 rounds, ask AI to analyze all your conversation histories with this prompt:
I've created 20 newsletters with you. I'm attaching all 20 conversation histories. Please analyze these conversations and extract: 1. What feedback did I give repeatedly? 2. What structures worked best? 3. What mistakes did you make that I corrected? 4. What patterns appear in my best newsletters? Use this analysis to create an improved prompt playbook that captures everything I've taught you through iteration.
This creates a playbook based on YOUR actual workflow, not generic best practices.
Customization ideas
The template above assumes a teaching-style newsletter built from a transcript. If yours is a different shape, adjust the structure section:
Curated / roundup newsletters
- Add section for "sources to cite"
- Include format for link formatting
- Add requirement for brief commentary on each item
Story-driven newsletters
- Emphasize narrative structure
- Add story framework (Past/Present/Future, SPAT, etc.)
- Include dialogue formatting
Tutorial / how-to newsletters
- Add numbered step format
- Include "common mistakes" section
- Add "next steps" requirement
Interview-based newsletters
- Include quote formatting
- Add requirement to credit guest
- Include key takeaways section
Troubleshooting common issues
Five problems come up over and over. Each has a one-line fix you add to the playbook:
- Output is too long
- Add stricter word count. Say "Maximum 600 words. Every word must earn its place."
- Output sounds generic
- Make your voice guide more specific. Add more "avoid" phrases.
- Structure is inconsistent
- Be more prescriptive about section lengths. "Hook: 2-3 sentences. Problem: 2 paragraphs max."
- Missing key details from transcript
- Add: "Include specific examples, quotes, or data points from the source material."
- CTA feels forced
- Either remove the CTA requirement or add: "Only include CTA if it flows naturally."
What's next
Build prompt playbooks for every content type you create regularly: short-form video scripts, YouTube scripts, social media posts, email sequences, course content. Each playbook means consistent output without starting from scratch.