Meeting Minutes Your Agent Writes in 3 Buckets: Decisions, Actions, Open Questions

Описание и применение

Скрипт преобразует сырые заметки встречи в структурированные протоколы с решениями, задачами и открытыми вопросами, обеспечивая ясность и назначение ответственных.

Задача

Raw meeting notes often produce minutes that are chronologically formatted but lack clear decisions, owners, and deadlines, making them useless for follow‑up.

Результат

Minutes now clearly state decisions, assign owners and deadlines to action items, and identify open questions, enabling attendees to know what they owe and what remains undecided.

Рабочий процесс

• 1. Define three buckets: Decisions, Action items, Open questions.
• 2. Require each decision to be an affirmative statement (e.g., "Decided to do X").
• 3. Require each action item to have an owner and a deadline; if missing, mark with [unassigned] or [TBD].
• 4. Require each open question to state what is undecided, what blocks it, and who owns the next step.
• 5. Open the minutes with a concise conclusion (max 3 lines).
• 6. Enforce length control: minutes body must be at most 1/3 the length of raw notes.
• 7. Perform a self‑check before output: verify all action items have owners/deadlines, decisions are affirmative, and open questions have next steps.
• 8. Output the minutes in Markdown, preserving brackets for missing data and avoiding invented details.

Доказательства

Minutes are not a transcript with better formatting. They exist so that someone who missed the meeting can catch up in 3 minutes — and so attendees know exactly what they owe.

Источник

If the notes name no owner, mark the item [unassigned]. If no deadline, mark [TBD].

Источник

The minutes body must be at most 1/3 the length of the raw notes.

Источник

Before returning anything, the agent verifies: does every action item have an owner? A deadline? Are decisions affirmative statements? Do open questions have a next step?

Источник