From soft-skills
Drafts professional emails using What-Why-How framework for software developers. Use for status updates, requests, escalations to colleagues, stakeholders, or leadership.
npx claudepluginhub melodic-software/claude-code-plugins --plugin soft-skillsThis skill is limited to using the following tools:
Generate a professional, well-structured email using communication best practices for software developers.
Drafts clear professional emails for cold outreach, follow-ups, internal memos, client updates, and networking with optimal subject lines, tone, length, and CTAs.
Drafts professional emails matching your writing style by analyzing sent emails via WorkIQ for tone, greetings, structure, and sign-offs. For replies, follow-ups, and proposals.
Guides software developers on professional communication: email structure, team messaging etiquette, meeting agendas, audience adaptation. Use for drafting messages, reports, updates.
Share bugs, ideas, or general feedback.
Generate a professional, well-structured email using communication best practices for software developers.
$ARGUMENTS - Optional context, topic, or existing draft to refine
If $ARGUMENTS is empty or insufficient, use AskUserQuestion to gather:
Question 1: Recipient Type (header: "Audience")
Question 2: Email Purpose (header: "Purpose")
Question 3: Urgency (header: "Urgency")
Use the What-Why-How structure:
WHAT (Opening - 1-2 sentences)
WHY (Context - 2-3 sentences)
HOW (Action - clear next steps)
Subject Line:
Body Structure:
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) |
Produce a complete email with:
## 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]
After presenting the draft, offer:
# 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
Present the draft in a clear format showing: