Debrief & Follow-up
SkillProductivityDebrief 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".
Available today. Use it from your connected AI after setup.
No other account needed.
Connect ahel once, and every AI you use reads what you have installed.
Then ask your AI: use the Debrief & Follow-up skill
What this skill tells your AI
The instructions your AI receives, as published by etrebels/claude-code-growth-os in .claude/skills/follow-up/SKILL.md and read by ahel’s review.
From a meeting note (point me at one in ops/ or demo/meetings/) or a pasted recap:
- Debrief (for you): decisions made, commitments — yours and theirs — and any new risk or signal. Offer to append it to
ops/daily-log.md. - 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.
Signals
- GitHub stars
- 20
- Forks
- 1
- Last commit
- Sep 2026
Advanced
- Catalog kind
- skill
- Gateway key
follow-up- Source
- github.com/etrebels/claude-code-growth-os