Ai Meeting Followup Brief

Turns rough meeting notes, transcript excerpts, or chat logs into a reliable follow-up brief with decisions, owners, deadlines, open questions, risks, and a ready-to-send recap draft.

Overview

AI Meeting Follow-up Brief helps a user turn messy meeting notes, transcript snippets, or chat logs into a practical execution artifact. It focuses on what happened after the discussion: confirmed decisions, commitments, action items, owners, deadlines, dependencies, open questions, and a concise recap message.

This skill is prompt-only and document-only. It does not join meetings, read calendars, send messages, access private transcripts, or verify facts outside the text the user provides. It must label uncertainty clearly instead of inventing decisions, owners, or dates.

When to Use

Use this skill when the user asks for help with:

• Turning meeting notes into action items
• Summarizing a meeting for follow-up
• Finding owners, deadlines, risks, and open questions from a transcript
• Drafting a post-meeting recap email or chat message
• Cleaning up rough notes after a team meeting, client call, class discussion, or project sync

Trigger phrases: "make follow-up action items from these notes", "summarize this meeting into next steps", "turn this transcript into a recap", "who owns what from this meeting", "draft a meeting follow-up message"

Required Inputs

Ask for the minimum useful context:

• Meeting notes, transcript excerpts, chat log, or bullet fragments
• Meeting purpose or project context
• Known participants and roles, if available
• Date of the meeting and intended audience for the recap
• Any known deadlines, constraints, or follow-up format preferences

If notes contain confidential, regulated, or third-party sensitive information, ask the user to confirm they are allowed to process and share it. If they cannot share full notes, work from a redacted summary and state the limitation.

Workflow

Step 1 - Confirm Scope and Source Quality

Identify what kind of source material the user provided: rough notes, transcript excerpt, chat log, agenda, or memory dump. State whether the source appears complete, partial, or fragmented.

Step 2 - Capture Meeting Context

Summarize the meeting purpose, date, participants, project, and intended audience. If any of these are missing, mark them as "not provided" rather than guessing.

Step 3 - Extract Confirmed Decisions

List only decisions that are explicitly supported by the notes. A decision should include the topic, the decision made, the evidence phrase or note fragment when useful, and any owner or deadline mentioned.

Step 4 - Identify Action Items

Extract commitments and next steps. For each action item, capture:

• Action
• Owner
• Deadline or timing
• Dependency
• Status: confirmed, inferred, or needs confirmation

Do not turn vague discussion into confirmed work. If the language is ambiguous, label it "needs confirmation."

Step 5 - Separate Open Questions

Create a separate list for unresolved topics, blockers, missing inputs, and questions that need a decision. Keep these distinct from action items.

Step 6 - Flag Risks and Ambiguities

Call out unclear ownership, missing deadlines, conflicting statements, dependencies, assumptions, and follow-up risks. Include a short note on what should be confirmed before sending the recap.

Step 7 - Build the Follow-up Brief

Produce the structured brief with these sections:

1. Meeting snapshot
2. Decisions made
3. Action items table
4. Open questions
5. Risks and ambiguities
6. Items needing confirmation
7. Suggested next check-in or milestone

Step 8 - Draft the Recap Message

Write a concise ready-to-send message for email, Slack, Teams, or another text channel. Keep the tone professional and neutral. Include a confirmation line such as: "Please reply if I missed or misassigned anything."

Step 9 - Add a Verification Checklist

Before the user sends the recap, include a short checklist:

• Are participant names and roles correct?
• Are action owners confirmed?
• Are dates and deadlines correct?
• Are uncertain items labeled clearly?
• Is confidential information removed or approved for sharing?
• Does the recap avoid adding decisions that were not made?

Output Format

Use this structure:

• AI Meeting Follow-up Brief
• Meeting Snapshot:
• Confirmed Decisions:
• Action Items:
• Open Questions:
• Risks and Ambiguities:
• Needs Confirmation:
• Ready-to-Send Recap Draft:
• Verification Checklist:

For action items, use a simple table when the channel supports it. If tables are not suitable, use bullets with owner, deadline, and status.

Safety Boundaries

• Do not fabricate decisions, owners, deadlines, attendance, quotes, or consensus.
• Label ambiguous items as "needs confirmation."
• Do not process or expose confidential, private, regulated, or third-party sensitive content unless the user confirms they are allowed to use it.
• Do not send the recap or contact participants. Provide draft text only.
• For legal, medical, HR, disciplinary, financial, or safety-critical meetings, recommend appropriate review before acting.

Quality Bar

A strong result lets the user immediately see who owns what, by when, what was actually decided, what remains unresolved, and what message can be sent after human review.

Example Prompts

1. From rough meeting notes: "Here are my notes from today's sprint planning: We decided to delay the payment feature to Q3. Alice will own the auth refactor, deadline June 15. Bob raised a concern about API rate limits but we didn't resolve it. Carol is on vacation next week. Turn this into a follow-up brief."

2. From a transcript excerpt: "I pasted part of our client call transcript below. We covered the Q2 roadmap, the client asked for a dashboard by end of month, and we agreed to a follow-up demo on the 28th. Can you extract the action items and draft a recap email?"

3. Quick standup summary: "We had a 15-minute standup. Three people gave updates. I need a quick bullet list of who's doing what, any blockers, and a Slack message I can post to the channel."