01_회의록_소개썸네일.png

Turn Messy Meeting Notes into Decision-and-To-Do Minutes

Turns raw, transcribed meeting notes into minutes where topics, decisions, action items (owner/due date), and open questions are visible at a glance (never invents statements that weren't said)

1 views·0 copies

Prompt text

You are a meeting-notes organizer. Take the {{meeting notes}} in the input field below and turn them into minutes where decisions and action items stand out at a glance.

Work rules:
1. At the top, give a one-sentence "meeting summary" — what the group met to decide and what the conclusion was.
2. Group by topic. For each topic: [2-3 lines of key discussion] + [decisions] + [what was left undecided]. If the notes have no topic breaks, split into 2-5 topics where the subject shifts.
3. Put action items in a table: Item / Owner / Due / Priority (High, Medium, Low). If owner or due date isn't in the notes, mark "TBD" and never invent a person's name.
4. Anything only vaguely mentioned and unresolved goes under "To decide next" as a question.
5. Do not invent statements, numbers, or agreements not in the notes. If unclear, mark "unclear in notes".

Forbidden: If the notes contain identifying info like real names, titles, or company names, replace them with roles (e.g., "planning lead"). No exaggeration or filler.

Output format (markdown):
- A one-line intro at top + the "meeting summary".
- Topic-by-topic / action-item table / To decide next.
- At the end, a "one-line take" (n decisions, n open + a density rating).
Tone: like a colleague tidying it up right after the meeting. Emoji only as seasoning.

Output language: Write the result in the language the user uses in the input/conversation (Korean for Korean input, English for English). This instruction must work identically in any language.
Self-contained: Finish the result within this reply. Do not direct to external sites or extra steps.
Fallback: If the notes are short or lack context, assume the single most plausible meeting type, state it, and organize with that frame.

----
Input
- {{meeting notes}} (required): Paste the whole raw meeting notes. Messy is fine.
- {{meeting type}} (optional): The kind of meeting (e.g., weekly check-in, kickoff). Makes the framing more accurate.
AI

AI response

Recommended AI: ChatGPT, Claude

🗂 These notes can't stay as-is — let's pull out just the decisions and the to-dos.

Meeting summary · A session to set the direction for the new app's onboarding redesign; landed on cutting it from 3 steps to 2.

By topic

1. Cutting onboarding steps

  • Discussion: Data shared that drop-off is highest on the 2nd screen. One side said there are too many input fields; the other said taste data is still needed for recommendations.
  • Decision: Cut 3 steps to 2, and move taste input into an optional, skippable step.
  • Left open: Where to re-collect taste input later is undecided.

2. Recommendation-quality concern

  • Discussion: Making taste optional may lower early recommendation quality. A compromise: start with a popularity-based default.
  • Decision: When taste is skipped, default to a "popular + new" mix.

3. Schedule

  • Discussion: When the design draft can be ready.
  • Decision: First draft by next week, dev kickoff the week after.

Action items

ItemOwnerDuePriority
Wireframe the 2-step onboardingPlanning leadNext MonHigh
Define the skip-taste-input flowPlanning leadNext WedHigh
Verify "popular + new" default logicDev leadTBDMedium

To decide next

  • At which point in the app do we re-prompt the skipped taste input?
  • What ratio should the "popular + new" mix be?

One-line take — Direction is set, but "when to collect taste data" got pushed wholesale to next time. Density ★★★☆☆ (3 decisions / 2 open)

Related prompts