# Followup

> Draft ready-to-send follow-up messages from a meeting recap — a recap email to all attendees and/or individual notes to each person reminding them of what they own. Use after a meeting when the user wants to send a summary or nudge people on their action items.

- Skill: `nord342/followup` (Agent Skill)
- Install (CLI): `npx skillmds@latest add nord342/followup`
- Raw SKILL.md: https://api.skillmd.com/api/skills/nord342/followup/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Productivity
- Author: nord342 (https://skillmd.com/u/nord342)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/nord342/followup

---


# Draft Follow-ups

Turn a recap into messages the user can actually send. Default to the most recent recap in `./Meetings/recaps/` unless `$ARGUMENTS` names a file or a person.

> Uses the follow-up structure in `${CLAUDE_PLUGIN_ROOT}/skills/meeting-notes/templates/followup.md` and pulls action items from the recap / `ACTIONS.md`.

## What to produce

Decide based on `$ARGUMENTS`:

- **No argument** → draft a **group recap email** to all attendees (TL;DR + decisions + everyone's action items) AND offer to generate per-person nudges.
- **A person's name** → draft a **personal note** to just that person, listing only the items they own, with due dates.
- **A recap file path** → use that meeting instead of the latest.

## Drafting rules

- **Match a normal professional tone** — warm, concise, skimmable. Not robotic, not over-formal. Short sentences. No corporate filler.
- Open with one line of context ("Thanks all for the product sync today — quick recap and who's doing what:").
- Put **action items as a checklist with owners and due dates** so they're unmissable.
- For personal nudges, lead with *their* items, keep it friendly, and make the ask explicit ("Could you get the pricing deck over by Fri?").
- Never invent details, names, or commitments not in the recap.
- Leave a clearly-marked placeholder for anything you can't know (e.g. `[your name]`, `[link to deck]`) rather than guessing.

## Output

Write drafts to `./Meetings/recaps/` next to the source recap, as `YYYY-MM-DD-<slug>-followup.md` (group) and/or `...-followup-<person>.md` (personal). Also show each draft inline in chat so the user can copy-paste immediately.

End by reminding the user these are **drafts to review and send themselves** — this plugin never sends anything, it just writes the message.

## Example

**User:** `/meeting-notes:followup Sarah`

**You:** produce a short personal note:

> **To:** Sarah
> **Subject:** Quick follow-up from today's product sync
>
> Hi Sarah — thanks for jumping in today. Two things on your plate from the sync:
>
> - [ ] Send the pricing deck — by **Fri Jul 3**
> - [ ] Confirm the Q3 launch date with marketing — by **Wed Jul 1**
>
> Shout if either needs a hand. Thanks!
> [your name]

Then: *"Drafted and saved to `Meetings/recaps/2026-06-29-product-sync-followup-sarah.md`. Want the group recap email too?"*