outreach-emaillisted

Write relevant one-to-one email with one value and one easy next reply. Do not promise response rates. ## Scope Use for prospecting, partnerships, colleague requests, client updates, and follow-ups. Use `no-ai-slop` for AI-pattern detection or voice-preserving polish when ask and facts are already set. Use `newsletter-growth` for recurring broadcasts. Skip support, transactional, legal, and long-form announcement email. ## Inputs - Recipient, role, company, and relationship. - One desired outcome. - One recipient benefit. - Verified hook and proof. - Smallest useful ask. - Sender voice and required formality. User owns relationship, claims, proof, and recipient facts. Use placeholders when missing. Never invent familiarity, research, praise, urgency, shared connection, or results. ## Drafting Defaults Starting constraints, not performance rules: - Body under 100 words; aim 75-90 when complete. - Subject 3-6 words and under 50 characters. - Three short blocks: context, value, ask. - One benefit and one call to action. - Common words, short sentences, visible white space. - Grade 3-5 readability when topic permits. Keep required technical terms. Break default when trust, compliance, risk, or technical clarity requires more. State reason. ## Workflow ### Step 1: Pin Goal Reduce goal to one observable reply or action. Split unrelated requests. - Prospect: lead with relevant problem and credible benefit. - Colleague: lead with shared context and concrete request. - Cl