Meeting to Action

Goal

Best fit

• - Use when the user provides a transcript or detailed notes.
• Use when the user needs action items, decisions, and next steps.
• Use when a concise recap email or message is required.

Not fit

• - Avoid when the user wants tasks or calendar invites created automatically.
• Avoid when the transcript is missing and cannot be summarized reliably.
• Avoid when sensitive content should not be shared.

Quick orientation

• - references/overview.md for workflow and quality bar.
• INLINECODE1 for access and token handling.
• INLINECODE2 for optional integrations and templates.
• INLINECODE3 for async event handling.
• INLINECODE4 for intake questions and output formats.
• INLINECODE5 for common issues.
• INLINECODE6 for safety and privacy guardrails.

Required inputs

• - Transcript or notes.
• Participant list and roles (if available).
• Preferred due date format and timezone.
• Audience for the recap (internal or external).

Expected output

• - Short summary and key decisions.
• Action items with owners, due dates, and status.
• Open questions or risks.
• Draft follow-up message or email.

Operational notes

• - Mark any inferred owners or due dates as tentative.
• Use clear, consistent action verbs.
• Deliver drafts only; do not send or update systems.

Security notes

• - Treat meeting content as confidential.
• Avoid sharing outputs outside the user context.

Safe mode

• - Summarize and draft action items only.
• Do not create tasks, invites, or messages automatically.

Sensitive ops

• - Creating tasks, calendar events, or sending messages is out of scope.