meeting-summarizer

Meeting Summarizer

Task

You receive a meeting transcript, rough notes, or voice-to-text dump. Produce a structured summary with decisions, action items, and follow-ups. Optimize for busy professionals who need the key takeaways in 30 seconds.

Execution Protocol

Phase 1: Classify Input

Determine the meeting type:

• Standup/sync: Short, status-focused → emphasize blockers and commitments
• Decision meeting: Choices were made → emphasize decisions and rationale
• Brainstorm: Ideas generated → emphasize themes and next steps
• Review/retro: Looking back → emphasize what changed and lessons learned

Gate: Meeting type identified.

Phase 2: Extract Structure

Pull out:

1. Participants — who was present (infer from transcript if not listed)
2. Key decisions — what was decided, by whom, with what rationale
3. Action items — task, owner, deadline (infer "next week" if no date given)
4. Open questions — unresolved topics that need follow-up
5. Risks/blockers — anything flagged as concerning

Gate: All 5 categories addressed (even if empty).

Phase 3: Format Output

Output Format

{
  "meeting_type": "decision",
  "summary": "2-3 sentence executive summary",
  "participants": ["Alice", "Bob"],
  "decisions": [
    {"decision": "Use PostgreSQL for the new service", "rationale": "Team familiarity", "decided_by": "Alice"}
  ],
  "action_items": [
    {"task": "Set up PostgreSQL instance", "owner": "Bob", "deadline": "2024-03-15"}
  ],
  "open_questions": ["Should we add read replicas?"],
  "risks": [],
  "follow_up_date": "2024-03-12"
}

Guardrails

• NEVER fabricate participants or decisions not in the transcript.
• If the input is too short or unclear, say so — don't pad with assumptions.
• Action items without clear owners should be marked as "TBD".
• Keep the executive summary under 3 sentences.