Meeting Notes to Action Plan

Most meetings end with good intentions and no record of who owns what. This skill turns messy notes into a structured action plan that survives contact with a busy week.

When to use this skill

Use this skill when:

• You have raw notes or a transcript from a meeting and need a shareable recap.
• A meeting produced decisions and next steps that are not yet written down.
• You want every action item to have a clear owner and due date before people leave the room.

Do not use it to summarize a meeting for the record only — the point is to produce owned, dated actions.

Inputs needed

• Raw meeting notes, a transcript, or a voice-memo summary.
• The list of attendees (and ideally their roles).
• The meeting's stated purpose, if known.
• Any hard deadlines or constraints mentioned.

Process

1. Read the notes once end to end before extracting anything.
2. Separate content into four buckets: decisions made, action items, open questions, and context worth keeping.
3. For each action item, assign a single owner. If no owner was named, flag it as OWNER NEEDED.
4. Assign each action item a due date. If none was given, propose one and mark it as (proposed).
5. Order action items by due date, then by owner.
6. List open questions separately so they are not mistaken for committed work.
7. Write a two-sentence summary at the top so a reader gets the gist without scrolling.

Prompt or workflow

You are turning meeting notes into an action plan.

Here are the notes:
"""
[PASTE NOTES OR TRANSCRIPT]
"""

Attendees: [LIST NAMES AND ROLES]
Meeting purpose: [PURPOSE OR "unknown"]

Produce:
1. A 2-sentence summary of what happened.
2. DECISIONS: a bullet list of decisions that were actually made.
3. ACTION ITEMS: a table with columns Owner | Action | Due date. Use a single
   owner per row. If no owner was named, write "OWNER NEEDED". If no date was
   given, propose one and append "(proposed)".
4. OPEN QUESTIONS: anything unresolved, kept separate from action items.

Rules:
- Do not invent decisions or commitments that are not in the notes.
- Prefer specific, verb-first action items ("Send", "Draft", "Confirm").
- Flag anything ambiguous rather than guessing.

Quality checklist

• Every action item has exactly one owner (or is flagged OWNER NEEDED).
• Every action item has a due date (real or (proposed)).
• Decisions are separated from action items.
• Open questions are not mixed in with committed work.
• Nothing was invented that is not supported by the notes.
• The top summary is readable in under 15 seconds.

Common mistakes

• Listing discussion topics as if they were decisions.
• Assigning an action item to a whole team instead of one person.
• Burying a hard deadline inside a paragraph instead of the due-date column.

Example output

Summary: The team agreed to ship the billing fix this week and paused the
reporting redesign until Q3. Two follow-ups are owner-pending.

Decisions:
- Billing fix ships before Friday.
- Reporting redesign deferred to Q3.

Action items:
| Owner        | Action                                   | Due date        |
|--------------|------------------------------------------|-----------------|
| Priya        | Deploy billing fix to production         | Thu             |
| OWNER NEEDED | Draft Q3 reporting scope                 | Next Mon (proposed) |

Open questions:
- Does the billing fix require a customer comms note?

Related skills

• Decision Memo Builder — when a meeting needs a documented decision, not just actions.
• Sales Call Follow-Up — for customer-facing calls specifically.
• Workflow Audit — when the same meeting keeps producing the same unfinished actions.

Attribution

This skill was created by Vectory and is licensed under CC BY 4.0.

Source: https://vectory.io/skills/meeting-notes-to-action-plan

Attribution: "Meeting Notes to Action Plan" by Vectory.