| name | context-aware-reply-drafting |
| description | Draft professional reply emails that reference the prior context of a business email thread. Use this skill when a user provides a thread of 3-5 messages and wants a reply that reads the conversation history, identifies the latest question or request, answers it directly, references relevant earlier context when helpful, and matches the tone of the original sender. Focus on concise professional reply drafting for standard business email threads. |
| metadata | {"environment":"communication-scheduling-operations","skill_id":"E6-LS2","short-description":"Draft email replies that reference prior conversation context","version":"1.0"} |
Context-Aware Reply Drafting
Use this workflow when an email reply needs to reflect what has already been said in a short business thread. The goal is to read the thread, identify what the latest email needs, draft a concise reply, reference the right prior context, and keep the tone aligned with the sender.
Scope: professional reply drafting for standard business email threads of 3-5 messages.
When to Use
Use this skill when:
- the user wants help replying to an email thread
- the reply needs to acknowledge prior discussion
- the latest email contains one or more questions or requests
- the result should sound professional and thread-aware
Reply Workflow
Follow these five steps.
Step 1 — Read the Entire Thread
Read the thread from oldest to newest before drafting the reply.
While reading, note:
- what has already been discussed
- any decisions or agreements already made
- open questions that still need a response
The reply should reflect the thread, not just the latest message in isolation.
Step 2 — Identify the Main Request in the Latest Email
Focus on the newest message and determine what it needs from the reply.
Common cases:
- a direct question
- a request for action
- several separate questions
- a follow-up on an earlier agreement
If the sender asked multiple things, list them first so the reply addresses all of them.
Step 3 — Draft a Direct Reply
Write a reply that answers the latest request clearly and efficiently.
Good structure:
- brief acknowledgment
- direct answer or response
- any next step if needed
Keep the reply concise. Do not restate the whole thread.
Step 4 — Reference Relevant Prior Context
Bring in earlier context only when it helps the reply make sense.
Good examples:
As discussed in your January 10 email...Following up on the agreement to...As you noted earlier in the thread...
You can also quote a short relevant fragment from a previous email when needed, but keep it brief.
Use prior context to:
- anchor the reply to the right part of the thread
- remind the reader of an earlier agreement or question
- connect the answer to what was already discussed
Step 5 — Match the Tone and Check Completeness
Before finalizing, review the tone and coverage.
Check:
- does the reply match the formality of the sender
- does it answer every question raised in the latest message
- is it concise rather than repeating the thread
The finished reply should sound professional, context-aware, and easy to send as written.
Basic Implementation Pattern
def draft_reply(latest_request, prior_context, tone):
opening = reference_context(prior_context)
body = answer_request(latest_request)
closing = choose_closing(tone)
return f"{opening}\n\n{body}\n\n{closing}"
Practical Rules
Read the Whole Short Thread First
For a 3-5 message thread, reading everything is usually the safest way to avoid missing context.
Answer the Latest Email Directly
The reply should solve the sender's current need, not just summarize the conversation.
Reference Prior Context Selectively
Use earlier emails to anchor the reply, but do not overload the message with repeated history.
Keep Replies Concise
A good reply should move the thread forward without rehashing every previous message.
Cover Every Question
If the sender asked multiple things, make sure none of them gets lost in the draft.
Common Pitfalls
- replying only to the latest sentence without reading earlier context
- repeating the entire thread instead of answering the current request
- mentioning prior context too vaguely
- missing one of several questions in the latest email
- using a tone that does not match the sender's level of formality
When NOT to Use
- the task is to analyze the thread rather than draft a reply
- the user wants a brand-new outbound email rather than a response
- the exchange is not a standard professional email thread
Quick Summary
1. Read the full thread
2. Identify the latest question or request
3. Draft a direct reply
4. Reference relevant prior context briefly
5. Match the sender's tone and verify all questions were answered
