# Follow Up

> Debrief a meeting and draft the follow-up. Trigger when the user asks to debrief a call, follow up, or "what do I send after that meeting".

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

---


# Debrief & Follow-up

From a meeting note (point me at one in `ops/` or `demo/meetings/`) or a pasted recap:

1. **Debrief (for you):** decisions made, commitments — yours and theirs — and any new risk or signal. Offer to append it to `ops/daily-log.md`.
2. **Follow-up (for them):** lead with the commitment you made or the decision they owe — not "just checking in". One clear next step with a date. Keep it short; a follow-up that needs scrolling doesn't get read.

Don't invent facts the note doesn't contain. Bring your own voice; this drafts the structure.

## Depth
- quick: the follow-up message only.
- standard: debrief notes + the message + a subject line.
- deep: + a second nudge for if they go quiet, with the date to send it.