Post-Meeting Recap Email

Build **post-meeting recap email** around the user’s actual constraints. Before producing the result for “post meeting recap email prompt”, identify missing facts and ask only the questions that block progress.

## Known information — Post-Meeting Recap Email
- [MESSAGE_GOAL] — for Post-Meeting Recap Email, supply the relevant message goal. If unavailable, label [MESSAGE_GOAL] `unknown`; never infer it.
- [KEY_DETAIL] — for Post-Meeting Recap Email, supply the relevant key detail. If unavailable, label [KEY_DETAIL] `unknown`; never infer it.
- [SIGN_OFF] — for Post-Meeting Recap Email, supply the relevant sign off. If unavailable, label [SIGN_OFF] `unknown`; never infer it.
- [RELATIONSHIP] — for Post-Meeting Recap Email, supply the relevant relationship. If unavailable, label [RELATIONSHIP] `unknown`; never infer it.
- [TONE] — for Post-Meeting Recap Email, supply the relevant tone. If unavailable, label [TONE] `unknown`; never infer it.
- [DEADLINE] — for Post-Meeting Recap Email, supply the relevant deadline. If unavailable, label [DEADLINE] `unknown`; never infer it.
- [REQUIRED_POINTS] — for Post-Meeting Recap Email, supply the relevant required points. If unavailable, label [REQUIRED_POINTS] `unknown`; never infer it.
- [MESSAGE_HISTORY] — for Post-Meeting Recap Email, supply the relevant message history. If unavailable, label [MESSAGE_HISTORY] `unknown`; never infer it.
- [MEETING_MATERIAL] — for Post-Meeting Recap Email, supply the relevant meeting material. If unavailable, label [MEETING_MATERIAL] `unknown`; never infer it.

## Working method — Post-Meeting Recap Email
1. Draft only after locking the audience, purpose, facts, voice, and desired action.
2. Deliver a publishable version plus a compact rationale for important choices.
3. Account for what has already been communicated and what response is realistically needed now.
4. Include a direct version and a softer alternative without changing the underlying facts.
5. Separate decisions, discussion, actions, owners, and unresolved questions.
6. Do not assign an owner or deadline unless the notes support it.
7. Remove pressure, filler, and invented familiarity.
8. Respect the relationship and what the recipient already knows.
9. State the purpose without a slow generic opening.
10. Include only details that help the recipient act.
11. Boundary for Post-Meeting Recap Email: Do not invent a relationship, urgency, prior conversation, offer, result, or personal detail.

## Final artifact — Post-Meeting Recap Email
- **Subject line for Post-Meeting Recap Email** — Post-Meeting Recap Email weak points, unknowns, and post meeting recap email prompt limits.
- **Email draft for Post-Meeting Recap Email** — post meeting recap email prompt → verify Post-Meeting Recap Email before use.
- **Short alternative for Post-Meeting Recap Email** — post meeting recap email prompt evidence → Post-Meeting Recap Email; omit preamble.
- **Tone note for Post-Meeting Recap Email** — material inputs for Post-Meeting Recap Email, each connected to post meeting recap email prompt.
- **Send check for Post-Meeting Recap Email** — ready-to-use Post-Meeting Recap Email, formatted for post meeting recap email prompt.

## Guardrails — Post-Meeting Recap Email
Audit the final Post-Meeting Recap Email against the original request. If an essential input is absent, say exactly how that limits the result.