Productivity

Transform raw meeting notes into a structured visual mind map that captures decisions, action items, open questions, and key discussion points so the team has a clear, shareable record.

MIND MAP CREATION INSTRUCTIONS:
1. Read through the full meeting notes and identify the central topic (the meeting's primary objective or theme).
2. Build the mind map with these branch categories radiating from the center:
   - DECISIONS MADE: Each decision as a node, with a sub-node for the rationale behind it.
   - ACTION ITEMS: Each action as a node, with sub-nodes for owner and deadline. Highlight overdue or unassigned items.
   - OPEN QUESTIONS: Unresolved items that need follow-up, with a sub-node for who should answer or when to revisit.
   - KEY DISCUSSION POINTS: Major topics discussed, with sub-nodes for supporting arguments, data cited, or dissenting views.
   - PARKING LOT: Ideas or tangents that were deferred for future meetings.
3. Use visual hierarchy:
   - Central node: Meeting title + date
   - Level 1: The five branch categories above
   - Level 2: Individual items
   - Level 3: Details (owners, dates, rationale)
4. Apply color coding:
   - Green: Completed or decided
   - Yellow: In progress or pending
   - Red: Blocked, overdue, or flagged concern

STYLE: Clean, professional, easy to share with team. Suitable for pasting into Slack, Notion, or a presentation. Use text-based formatting (indented hierarchy with symbols) unless a specific visual tool is requested.

OUTPUT CONSTRAINTS:
- Present the mind map in a clear indented text format using lines and connectors (e.g., arrows, dashes, or box-drawing characters).
- List all action items again at the bottom in a simple table: Action | Owner | Deadline | Status.
- If notes are ambiguous, flag items with "[UNCLEAR -- verify]" rather than guessing.
- Keep the map to one "page" -- concise labels, not full paragraphs.

---

MY INFO:

Meeting Name/Topic: (required)

Date: (required)

Attendees: (required)

Meeting Notes (paste below): (required)

Preferred Output Format (text hierarchy / Mermaid diagram / Markmap): (optional)