meeting-follow-up-draft

$npx mdskill add Significant-Gravitas/skills-catalog/meeting-follow-up-draft

Use this after a meeting, from the principal's notes or a transcript.

SKILL.md

.github/skills/meeting-follow-up-draftView on GitHub ↗
---
name: "meeting-follow-up-draft"
description: "Draft a follow-up with decisions, owners, dates, and open questions from meeting notes."
triggers: ["meeting follow-up", "action items", "send notes", "recap email", "meeting summary"]
version: "1"
---

# Meeting follow-up draft

Use this after a meeting, from the principal's notes or a transcript.

## Pull decisions and actions

Read the notes and list:

- decisions made, in plain words;
- actions, each with an owner and a due date as stated;
- questions left open, and who raised them.

Record only what the notes show. If the notes are empty or partial, say so and
ask the principal for the missing points.

## Draft the follow-up

Draft a short email in the principal's voice to the attendees. Open with the
decisions, then the actions as a list with owner and date, then open
questions. Keep it neutral; do not add promises that were not made in the
room. Leave out anything said in confidence or not meant for all attendees.

## Items with no owner

List actions with no owner or no date, separately, for the principal to
assign. Do not pick an owner or a date yourself. Note any action that the
principal took on, so it goes on their own list.

Never send the follow-up without a clear yes. Do not invent a decision,
owner, date, or quote, and keep private notes private.

More from Significant-Gravitas/skills-catalog

SkillDescription
account-health-and-qbrsUse when a support account wobbles or a quarterly business review looms: read the health signals, run the success plan, and prep the review from evidence.
accounts-receivable-follow-upReview open receivables and draft factual, staged payment follow-ups without inventing status or contacting a customer.
ad-copy-variantsWrite ad variants that each test one idea, within platform limits and supported claims.
alex-getting-startedUse on the first conversation with Alex, or whenever their memory has no product preferences yet: learn what the user is building and who for, where specs, roadmap and numbers live, who decides dates and scope, and get them to a first real product deliverable.
alliance-co-commercializationUse when a strategic alliance needs joint selling governance: operating model, joint targeting, steering prep, and milestone accountability.
anika-getting-startedUse on the first conversation with Anika, or whenever their memory has no partnership preferences yet: learn which partners and alliances the user owns, what motion they run, and get one real partner read on screen in the same session.
assure-partner-led-deliveryUse when partners deliver client work in your name: own the in-flight book, run the weekly delivery review, and rescue engagements before clients feel it.
automate-finance-reportingUse to connect a number source, map an export into the finance ledger, or QA a sheet: the column mapping, the dedupe key, the load summary, and the checks that must pass before a read ships.
billing-refunds-and-exceptionsUse when money is on the table: verify the charge, check the policy, and stage a refund or exception draft that stops at the owner's yes.
board-and-investor-metrics-briefPrepare a concise board or investor metrics brief with definitions, sources, comparisons, drivers, risks, and decisions needed.