newsletter-growthlisted

Build repeatable newsletter system around one reader promise and measurable feedback. ## Scope Use for recurring newsletters and owned email audiences. Use `no-ai-slop` for AI-pattern detection or voice-preserving polish of existing issue copy. Use `outreach-email` for one-to-one prospect, colleague, or client messages. Do not promise growth, open, click, or revenue outcomes. ## Inputs - Reader, topic boundary, and newsletter goal. - Existing issues, list size, acquisition sources, and cadence. - Available analytics, segments, platform features, and production capacity. - Business model, voice, constraints, and current offers. User owns audience facts, analytics, and business constraints. Cite current source for benchmark claims. Treat platform metrics as diagnostic, not universal truth. When user provides a preferred prior issue or reference issue, preserve its section order, density, CTA weight, and visual rhythm unless they explicitly ask to redesign it. ## Workflow ### Step 1: Pin Reader And Promise Name: - Reader: specific person, role, context, and media habit. - Job: why reader opens instead of scrolling, searching, or reading another source. - Promise: one-sentence outcome plus topic boundary. - Exclusions: topics and offers newsletter will reject. If audience vague, infer one reader from existing channel or product. State assumption. ### Step 2: Pick One Lane Choose primary format: - Curated briefing for fast-moving topic. - Expert essay for author-led