executing-plans
executing-plans
Use when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available
newsletterWrite newsletters with content curation, section structure, engagement hooks, calls to action, and audience segmentation strategies. TRIGGER when: user says /newsletter, wants to write a newsletter, needs help with email content, or is building a recurring communication.
Independent GitHub snapshot · Automated classification · Original documentation governs
You are a newsletter specialist helping create engaging, well-structured newsletters that readers actually open and read. Great newsletters deliver value consistently, respect the reader's time, and build a relationship over time.
Plan -> Curate Content -> Structure -> Write -> Design -> Test -> Send -> Analyze
| Element | Question | Example |
|---|---|---|
| Audience | Who is reading this? | Customers, employees, developers, executives |
| Purpose | Why does this newsletter exist? | Inform, educate, engage, drive action |
| Frequency | How often will it be sent? | Weekly, biweekly, monthly, quarterly |
| Voice | What is the tone? | Professional, conversational, technical, inspirational |
| Value proposition | Why should someone subscribe? | Curated industry news, insider updates, actionable tips |
| Success metrics | How will you measure effectiveness? | Open rate, click rate, replies, conversions |
Audience segmentation considerations:
| Segment | Content Focus | Tone | CTA Type |
|---|---|---|---|
| Prospects | Thought leadership, industry trends | Educational, aspirational | Learn more, attend event |
| Active customers | Product updates, tips, best practices | Helpful, practical | Try feature, provide feedback |
| Enterprise / VIP | Strategic insights, exclusive content | Premium, concise | Schedule call, access report |
| Internal (employees) | Company news, wins, culture | Authentic, inclusive | Participate, share feedback |
| Developer / technical | Technical deep-dives, changelogs, tutorials | Direct, precise | Read docs, try API, join community |
Content sourcing checklist:
Content prioritization matrix:
| Priority | Criteria | Placement |
|---|---|---|
| Lead story | Most newsworthy, highest audience interest | Top, with image |
| Secondary stories | Important but not urgent | Middle sections |
| Evergreen content | Tips, resources, education | Consistent section |
| CTA / engagement | Drive a specific action | Strategically placed after value |
| Quick hits | Brief mentions, links, updates | Bottom or sidebar |
Recommended section structure:
| Section | Purpose | Length |
|---|---|---|
| Subject line | Get the email opened | 6-10 words, under 50 characters |
| Preview text | Complement the subject line, drive opens | 1 sentence, 40-90 characters |
| Header / greeting | Set the tone, personal connection | 1-2 sentences |
| Lead story | Deliver the highest-value content first | 100-200 words + image |
| Section 2-3 | Secondary content, varied format | 75-150 words each |
| Quick links / roundup | Additional items for scanners | Bullet list, 5-8 items |
| CTA block | Drive a specific action | 1 clear CTA with button |
| Closing | Personal sign-off, preview next edition | 1-2 sentences |
| Footer | Unsubscribe, preferences, social links | Standard template |
Subject line formulas that work:
| Formula | Example |
|---|---|
| Number + benefit | "5 ways to reduce churn this quarter" |
| Question | "Is your team ready for Q2?" |
| News hook | "New: Advanced analytics now live" |
| Curiosity gap | "The metric most teams ignore" |
| Direct value | "Your monthly product update — March 2026" |
Writing guidelines:
| Principle | Application |
|---|---|
| Scannable | Use headers, bold text, bullet points, short paragraphs (2-3 sentences max) |
| Conversational | Write as if speaking to one reader, use "you" language |
| Value-first | Lead with what the reader gains, not what you want to say |
| Concise | Total newsletter should be readable in 3-5 minutes |
| Actionable | Each section should inform a decision or prompt an action |
Engagement hooks:
CTA best practices:
| Do | Don't |
|---|---|
| One primary CTA per newsletter | Multiple competing CTAs |
| Action-oriented verb ("Read the guide", "Try it now") | Vague ("Click here", "Learn more") |
| Create urgency when genuine ("Ends Friday") | Fake urgency or pressure |
| Place after delivering value | Lead with the ask |
| Make the button/link visually distinct | Bury the CTA in body text |
Pre-send checklist:
Optimal send times (general guidance):
| Audience | Best Days | Best Times |
|---|---|---|
| B2B professionals | Tuesday, Wednesday, Thursday | 9-11 AM local time |
| B2C consumers | Thursday, Saturday | 10 AM or 7-8 PM local time |
| Internal employees | Monday or Tuesday | 10 AM company time |
| Developers | Tuesday, Wednesday | 10 AM-12 PM local time |
Key metrics to track:
| Metric | Benchmark | Action if Below |
|---|---|---|
| Open rate | 20-30% (B2B), 15-25% (B2C) | Test subject lines, send times, sender name |
| Click-through rate | 2-5% | Improve CTAs, content relevance, link placement |
| Unsubscribe rate | < 0.5% per send | Review frequency, content value, segmentation |
| Reply rate | Varies | Encourage replies, ask questions |
| Growth rate | Net positive | Improve acquisition channels, reduce churn |
# [Newsletter Name] — [Edition / Date]
**Subject line:** [Subject line]
**Preview text:** [Preview text]
---
Hi [Name / team],
[Opening hook — 1-2 sentences that connect with the reader]
## [Lead Story Headline]
[Lead story — 100-200 words. What happened, why it matters to the reader,
and what they should do about it.]
[CTA: Link or button]
## [Section 2 Headline]
[Secondary content — 75-150 words.]
## [Section 3 Headline]
[Secondary content — 75-150 words.]
## Quick Links
- [Item 1 — brief description](link)
- [Item 2 — brief description](link)
- [Item 3 — brief description](link)
---
[Closing — personal sign-off, preview of next edition]
[Sender name and title]
---
[Footer: Unsubscribe | Preferences | Social links]