email-writer

Purpose

[TODO: Add purpose description]

MANDATORY WORKFLOW (MUST FOLLOW EXACTLY)

Step 1: Initial Analysis (Gather Context) (REQUIRED)

YOU MUST:

1. Determine the purpose of the email: update, request, announcement, escalation, follow-up, or response
2. Identify the audience: who are the recipients (TO, CC, BCC) and what are their roles and technical familiarity
3. Assess urgency: is this time-sensitive, routine, or informational
4. Establish tone requirements: formal executive communication, casual team update, diplomatic escalation, celebratory announcement
5. Ask clarifying questions if context is incomplete:
   • What is the key message or ask?
   • Who needs to take action and by when?
   • Is there sensitive information that requires careful framing?
   • What prior communication has occurred on this topic?

DO NOT PROCEED WITHOUT UNDERSTANDING PURPOSE AND AUDIENCE

Step 2: Load Memory

Load project-specific memory via MemoryStore interface:

memoryStore.getSkillMemory("email-writer", project)

⚠️ STEP 2: Structure Content (REQUIRED)

YOU MUST:

1. Organize key points in order of importance — lead with the most critical information
2. Determine email format based on type:
   • Status Update: Progress summary, milestones, blockers, next steps
   • Request: Clear ask, context/justification, deadline, fallback options
   • Announcement: What changed, why it matters, impact, action required
   • Escalation: Issue summary, impact, actions taken, help needed, urgency
   • Follow-up: Reference prior discussion, decisions made, action items, deadlines
   • Response: Acknowledge receipt, address each point, provide answers or commitments
3. Plan structure: subject line, greeting, opening statement, body sections, action items, closing
4. Identify supporting details: data points, links, attachments to reference

DO NOT PROCEED WITHOUT A CLEAR CONTENT STRUCTURE

⚠️ STEP 3: Compose Email (REQUIRED)

YOU MUST:

1. Write the subject line:
   • Keep under 60 characters when possible
   • Include category prefix when appropriate: [Action Required], [FYI], [Update], [Urgent]
   • Be specific: "Q4 API Migration Timeline Update" not "Update"
2. Write the greeting: Match formality to audience and relationship
3. Write the body:
   • Opening sentence states the purpose immediately
   • Use short paragraphs (2-4 sentences each)
   • Use bullet points or numbered lists for multiple items
   • Bold or highlight key dates, decisions, and action items
   • Include necessary context without over-explaining
4. Write action items (if applicable):
   • Clearly state who needs to do what by when
   • Use a distinct section or formatting for visibility
5. Write the closing:
   • Summarize the key ask or next step
   • Include appropriate sign-off matching tone
   • Add signature block

DO NOT USE VAGUE OR AMBIGUOUS LANGUAGE

⚠️ STEP 4: Review & Polish (REQUIRED)

YOU MUST validate the email against these criteria:

1. Clarity check:
   • Purpose is stated in the first two sentences
   • Each paragraph serves a distinct purpose
   • No jargon without explanation for non-technical recipients
   • No ambiguous pronouns or references
2. Tone check:
   • Tone matches the audience and situation
   • No passive-aggressive phrasing
   • Appropriate level of formality
   • Empathetic where needed (delays, incidents, bad news)
3. Completeness check:
   • All questions from the user's request are addressed
   • Action items include owners and deadlines
   • Relevant context and links are included
   • CC/BCC recipients are justified
4. Actionability check:
   • Recipients know exactly what is expected of them
   • Response deadline is clear (if applicable)
   • Escalation path is mentioned (if applicable)
5. Present the final email to the user for review
6. Offer alternatives: Provide 2-3 alternative subject lines and note any tone adjustments available

DO NOT SKIP VALIDATION

OPTIONAL: Update Project Memory

If project-specific communication patterns are discovered during the process, use memoryStore.update(layer="skill-specific", skill="email-writer", project="{project-name}", ...) to store insights:

• Preferred communication style and conventions
• Common recipients and distribution lists
• Project-specific terminology and acronyms
• Recurring email types and templates

Timestamps and staleness tracking are handled automatically by MemoryStore. See MemoryStore Interface.

---

Step 5: Generate Output

Create deliverables and save to /claudedocs/:

• Follow OUTPUT_CONVENTIONS.md naming: email-writer_{project}_{YYYY-MM-DD}.md
• Include all required sections
• Provide clear, actionable recommendations

Compliance Checklist

Before completing ANY email composition, verify:

• Step 1: Context gathered — purpose, audience, urgency, and tone established
• Step 2: Content structured — key points organized, format determined
• Step 3: Email composed — subject, greeting, body, action items, and closing written
• Step 4: Email reviewed — clarity, tone, completeness, and actionability validated

FAILURE TO COMPLETE ALL STEPS INVALIDATES THE EMAIL

---

Special Case Handling

Sensitive Topics

When composing emails about sensitive matters (layoffs, performance issues, security incidents):

1. Use neutral, factual language — avoid blame or emotional phrasing
2. Consult HR or legal guidance references if available
3. Limit distribution to need-to-know recipients
4. Avoid including sensitive details in subject lines
5. Offer to draft multiple versions for different audience levels

Cross-Cultural Communication

When composing emails for international or cross-cultural teams:

1. Avoid idioms, slang, or culture-specific references
2. Use explicit language — do not rely on implied meaning
3. Be mindful of time zone references — include UTC offsets
4. Use inclusive greetings appropriate for the audience
5. Consider directness norms — some cultures prefer indirect communication

Escalation Emails

When composing escalation emails to management or leadership:

1. Lead with impact — business consequences, customer effect, timeline risk
2. Summarize actions already taken — demonstrate due diligence
3. State the specific help needed — don't leave it ambiguous
4. Provide options with trade-offs when possible
5. Maintain professional tone — urgency without alarm

---

Further Reading

Refer to official documentation and resources:

• Business Communication:
  • Harvard Business Review on Email: https://hbr.org/topic/communication
  • Plain Language Guidelines: https://www.plainlanguage.gov/
• Technical Communication:
  • Google Developer Documentation Style Guide: https://developers.google.com/style
  • Write the Docs: https://www.writethedocs.org/
• Best Practices:
  • Email Charter: http://www.emailcharter.org/
  • Getting Things Done (GTD) Email Methodology

---

Version History

• v1.1.0 (2026-02-10): Phase 4 Migration
  • Migrated to interface-based patterns (ContextProvider + MemoryStore)
  • Removed hardcoded filesystem paths
  • Added interface references section
• v1.0.0 (2025-01-XX): Initial release
  • Mandatory 4-step workflow for email composition
  • Audience analysis and tone calibration
  • Support for status updates, requests, announcements, escalations, and follow-ups
  • Project memory integration for communication pattern persistence
  • Template-based output formatting