$ cat prompt.txt — Newsletter & Substack

Newsletter First 10 Issues — Plan + Draft to Beat Week-3 Burnout

Plan and draft your first 10 newsletter issues so you launch with a buffer and never miss a send.

2–4 hours intermediate Claude Opus, GPT-5#newsletter#content-planning#substack

intro.md

Most newsletters die at issue 3 — the founder runs out of ideas the moment growth feels slow. The fix is launching with a buffer. This prompt plans your first 10 issues around content pillars and drafts the structure of each, so you start with momentum instead of a blank page every week.

$ cat prompt.txt | pbcopy

The prompt — copy & paste

prompt.txt

You are a newsletter strategist who's grown multiple newsletters past 25k subscribers. Plan and structure my first 10 issues so I launch with a buffer and never face blank-page panic.

INPUTS:
- Niche: {{niche}}
- Audience (who they are + what they want from me): {{audience}}
- My angle / unique perspective: {{your_angle}}
- Cadence: {{cadence}} (weekly / bi-weekly)

PRODUCE:

1. NEWSLETTER POSITIONING
- One-line positioning: "The newsletter for {{audience}} who want [outcome]"
- A consistent issue STRUCTURE/format readers will come to expect (e.g. one big idea + 3 links + a tool of the week)
- Your "voice" in 3 rules

2. CONTENT PILLARS (4-5)
The recurring buckets you rotate so you never run dry — each tied to what {{audience}} actually wants. (e.g. tactical how-to, curated finds, contrarian take, case study, Q&A.)

3. FIRST 10 ISSUES
For each issue:
- Issue # + subject line (+1 alt) — make subject lines curiosity/benefit-driven
- The pillar it belongs to
- The ONE core idea/takeaway
- A 4-6 bullet outline of the issue's content
- The CTA (reply prompt, share ask, or soft product mention)
Issue 1 should be a strong "why this newsletter exists + what you'll get" opener that also delivers immediate value. Sequence the 10 so the strongest, most shareable ideas land early (issues 1-4 drive your initial word-of-mouth).

4. GROWTH HOOKS
2-3 issues that are designed to be SHARED (a strong framework, a useful resource, a contrarian take) — flag which and why.

5. BUFFER STRATEGY
How to stay 2-3 issues ahead so a busy week never breaks the streak.

Match {{your_angle}} throughout — generic content is what AI newsletters drown in; YOUR perspective is the moat.

$ variables_to_fill_in

$ man playbook

Step-by-step playbook

How to actually use this prompt for the best results.

01
Lock a repeatable issue structure
Readers subscribe to a format they can rely on. Commit to the structure from Stage 1 (e.g. 'one idea + 3 links + a tool') so every issue is faster to write and readers know what they're getting.
02
Draft issues 1-4 fully before launching
Launch with a buffer. Having the first 4 issues drafted means the early weeks — when growth feels slow and motivation dips — don't break your streak. Consistency in the first 8 weeks is what separates newsletters that survive.
03
Front-load your most shareable ideas
Your initial subscribers share (or don't) based on the first few issues. Put the strongest, most forward-able ideas (the growth hooks) in issues 1-4 to seed word-of-mouth early.
04
Always stay 2-3 issues ahead
Use the buffer strategy to maintain a 2-3 issue lead. The newsletters that die are the ones written the night before — a buffer turns a busy week from a missed send into a non-event.

$ man tips

Pro tips for better output

›Your unique angle is the only defense against the flood of generic AI newsletters — lean into your specific perspective and lived experience, not summarized news.
›Reply-prompt CTAs ('hit reply and tell me X') boost deliverability (engagement signal) AND give you content ideas + testimonials.
›Subject lines drive opens more than anything — write 2-3 per issue and keep a swipe file of the ones that performed.

$ echo $YIELD

What you'll get

output.md

Newsletter positioning + a repeatable issue format, 4-5 content pillars, 10 fully-outlined issues (subject + pillar + core idea + bullet outline + CTA), flagged growth-hook issues, and a buffer strategy.

$ man faq

FAQ

How many issues should I have ready before launching?

At least the first 3-4 fully drafted. The most common newsletter death is week-3 burnout when growth feels slow and you're writing the night before. A buffer carries you through the discouraging early weeks where consistency matters most.

Weekly or bi-weekly to start?

Bi-weekly if you have under ~5 hours/week — a great bi-weekly newsletter beats a rushed weekly one that you'll resent. You can always increase cadence once the system is established. Consistency at any cadence beats sporadic 'whenever I have time'.

$ ls /prompts/newsletter