Skip to main content
command CX Codex

compose-email — Claude Code command: structured emails with What-Why-How

compose-email — a command for drafting professional emails using the What-Why-How framework. Provide context and get a ready-to-send draft with clear structure, matching tone, and concrete next steps.

MIT ★ 2,707 updated 2026-03-05

Install into Claude Code · Manually: put the files in place All methods and platforms ↓
.claude/commands/compose-email.md
Open on GitHub

What compose-email does

The command applies a proven framework: WHAT (lead with your main point), WHY (explain relevance to the recipient), HOW (specific call-to-action). It builds the email with audience awareness — technical peers get jargon, executives get outcome focus, cross-functional teams get translation.

The workflow starts with questions about recipient type, email purpose (status update, request, announcement, escalation), and urgency level. Then it generates a scannable subject line and body structured with bullets, bold highlights, and a clear next step. After the draft, it offers refinement options: adjust formality, expand or trim content, translate jargon, or reformat for Slack or Teams.

Install by adding the command file to your editor's commands directory. Built for Claude Code; companion integrations for Codex, GitHub Copilot, and Gemini CLI are in their respective project folders.

What it helps with

  • write an email that gets noticed and acted on, not buried
  • structure a complex request without throat-clearing or hedging
  • match tone to audience — from peers to leadership
  • craft a subject line that scans at a glance
  • generate a draft and refine it in one or two rounds

Example prompts for the agent

  • Draft an email to my tech lead asking for a deadline extension on the API migration
  • Help me write a sprint completion status update for stakeholders
  • Compose an email to the team about the production issue and our resolution plan

How to install compose-email

Manually: put the files in place

.claude/commands/compose-email.md

Call it with /compose-email. For all projects use ~/.claude/commands/

Questions about compose-email

How do I install compose-email in Claude Code?

Copy the .claude/commands/compose-email.md file from the repository into the .claude/commands/ folder of your project. Then call /compose-email with context, or without it if you want the agent to ask clarifying questions.

What does compose-email do?

It generates a professional email draft using the What-Why-How framework. It asks about your recipient type and email purpose, then produces a draft with subject line, structured body, and call-to-action tuned to your audience's expectations.

What audience types does the command handle?

Four types: technical peers (high jargon), non-technical stakeholders (plain language), cross-functional teams (balanced explanation), and leadership (outcome-focused). Tone and detail level adjust for each.

Source text

compose-email.md · MIT
---
description: Draft a professional email using the What-Why-How framework. Use when you need to compose emails to colleagues, stakeholders, or leadership.
argument-hint: [context or paste existing draft]
allowed-tools: Read, AskUserQuestion
---

# Draft Professional Email

Generate a professional, well-structured email using communication best practices for software developers.

## Arguments

`$ARGUMENTS` - Optional context, topic, or existing draft to refine

## Workflow

### Step 1: Gather Context

If `$ARGUMENTS` is empty or insufficient, use AskUserQuestion to gather:

**Question 1: Recipient Type** (header: "Audience")

- Technical peer (developer, engineer)
- Non-technical stakeholder (PM, executive, customer)
- Cross-functional team (mixed audience)
- Manager or leadership

**Question 2: Email Purpose** (header: "Purpose")

- Status update or progress report
- Request (review, approval, resources)
- Information sharing (FYI, announcement)
- Escalation or raising concern
- Following up on prior conversation

**Question 3: Urgency** (header: "Urgency")

- Urgent - needs response today
- Standard - within 1-2 days
- Low priority - for awareness only

### Step 2: Apply Communication Framework

Use the **What-Why-How** structure:

1. **WHAT** (Opening - 1-2 sentences)
   - Lead with the key message or request
   - State the purpose immediately
   - No throat-clearing ("I hope this email finds you well...")

2. **WHY** (Context - 2-3 sentences)
   - Provide necessary background
   - Explain relevance to the recipient
   - Include only essential context

3. **HOW** (Action - clear next steps)
   - Specific call-to-action
   - Clear deadline if applicable
   - Who needs to do what

### Step 3: Apply Email Best Practices

**Subject Line:**

- Specific and scannable (5-8 words ideal)
- Include action needed: "[Action Required]", "[FYI]", "[Decision Needed]"
- Include deadline if urgent: "[Due Friday]"

**Body Structure:**

- Bullets for multiple points (3-5 max)
- Bold key information
- One topic per email
- Short paragraphs (2-3 sentences max)

**Tone Calibration by Audience:**

| Audience | Tone | Jargon Level |
| --- | --- | --- |
| Technical peer | Direct, precise | High (use technical terms) |
| Non-technical | Business-focused | Low (translate jargon) |
| Cross-functional | Balanced | Medium (explain as needed) |
| Leadership | Concise, impact-focused | Low (focus on outcomes) |

### Step 4: Generate Draft

Produce a complete email with:

```markdown
## Email Draft

**Subject:** [Clear, specific subject line]

---

[Opening - WHAT: Key message/request]

[Context - WHY: Background and relevance]

[Body - Details as needed, use bullets for lists]

[Closing - HOW: Clear call-to-action]

[Sign-off]
```

### Step 5: Offer Refinements

After presenting the draft, offer:

1. **Tone adjustment** - Make more/less formal
2. **Length adjustment** - Expand or condense
3. **Jargon translation** - Adjust technical language level
4. **Format change** - Different structure for different medium (Slack, Teams)

## Example Usage

```bash
# With context
/soft-skills:draft-email Need to ask team lead for deadline extension on API migration

# Refine existing draft
/soft-skills:draft-email "Hi team, wanted to let you know about the deployment..."

# Start fresh
/soft-skills:draft-email
```

## Output

Present the draft in a clear format showing:

1. **Subject line** with rationale
2. **Email body** with WHAT/WHY/HOW sections labeled
3. **Refinement options** for iteration

## Anti-Patterns to Avoid

- Generic subjects ("Quick question", "Update", "FYI")
- Burying the request at the end
- Wall of text without structure
- Missing clear call-to-action
- Over-apologizing or excessive hedging
- CC'ing unnecessarily

© softaworks · MIT · softaworks/agent-toolkit

Similar slash commands

All slash commands for Notes, tasks and projects →

From the same set79

The whole set →
gepetto gepetto turns a Markdown spec into an implementation plan, using research, user interviews, and reviews from Gemini and Codex. Use it before building a feature that needs careful planning. CX Codex +1 1,600installs web-to-markdown web-to-markdown converts JavaScript-heavy web pages into clean Markdown via a local browser CLI. Helpful for archiving articles and docs without layout junk. CX Codex +1 796installs communication-excellence-coach communication-excellence-coach reviews communication drafts, calibrates tone for different audiences, and runs roleplay practice for difficult conversations. CX Codex ★ 2,707repo stars sync-branch Syncs a feature branch with the latest main via rebase. Runs on /sync-branch and updates the PR with force-push. CX Codex +1 ★ 2,707repo stars viral-tweet viral-tweet converts rough draft thoughts into high-engagement posts tailored to the recommendation system of X. CX Codex +1 ★ 2,707repo stars sync-skills-readme sync-skills-readme scans skills/ and refreshes the Available Skills table in the root README.md. Use it after adding or changing skills. CX Codex +1 ★ 2,707repo stars explain-pr-changes explain-pr-changes — a command that generates detailed pull request summaries with architectural visualizations. Helps reviewers grasp the essence and impact of changes in minutes. CX Codex +1 ★ 2,707repo stars explain-changes-mental-model explain-changes-mental-model splits a diff into logical groups and gives an order to read them in, so a big commit or branch turns into something you can follow. CX Codex +1 ★ 2,707repo stars

Project sponsors

Companies that keep this analytics open