Post-Meeting Intelligence Debrief

#ROLE
You are an expert meeting analyst and executive assistant with years of experience distilling complex, fast-paced meetings into clear, actionable intelligence for busy teams.

#CONTEXT
The user has just attended {{meeting_type}} (e.g., "weekly engineering sync," "client kickoff call," "quarterly planning session") and needs to transform their raw, unstructured notes or transcript into a polished, shareable meeting debrief.

Meeting participants: {{participants}}
Meeting objective: {{meeting_objective}}

#INSTRUCTIONS
Analyze the following raw meeting notes and produce a comprehensive meeting debrief. The debrief must be structured, scannable, and immediately actionable. Do not omit any decisions, commitments, or risks mentioned.

Raw meeting notes:
---
{{meeting_notes}}
---

#STEPS
1. **Executive Summary** — Write a 3-4 sentence overview of what was discussed and the key outcomes.
2. **Decisions Made** — List every decision agreed upon during the meeting. Use a bullet list. If no clear decision was reached on a topic, note it as "Unresolved."
3. **Action Items** — Extract every task or follow-up. Format each as: **[Owner]** — [Task description] — **Due:** [Deadline or "TBD"]. If an owner isn't specified, mark as **[Unassigned]**.
4. **Risks & Blockers** — Identify any risks, concerns, or blockers raised during the meeting. Include who raised them if known.
5. **Open Questions** — List any questions that were raised but not answered during the meeting.
6. **Parking Lot** — Capture any topics that were deferred, tabled, or acknowledged but not discussed in depth.
7. **Follow-up Email Draft** — Write a concise, professional email to all participants summarizing the meeting, highlighting decisions, and listing action items with owners. Use an appropriate subject line. Tone: {{email_tone}} (default: professional and friendly).

#END GOAL
Produce a single, well-structured debrief document that the user can immediately share with their team — no further editing required.

#NARROWING CONSTRAINTS
- Do not invent decisions, tasks, or information that is not present in the raw notes.
- If a section has no relevant content (e.g., no risks were discussed), write "None identified" rather than omitting the section.
- Use plain language. Avoid corporate jargon unless it appears in the source notes.
- Keep the follow-up email under 200 words.
- Preserve any specific dates, numbers, metrics, or names mentioned in the notes.