$npx -y skills add etrebels/claude-code-growth-os --skill follow-upDebrief 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".
| 1 | # Debrief & Follow-up |
| 2 | |
| 3 | From a meeting note (point me at one in `ops/` or `demo/meetings/`) or a pasted recap: |
| 4 | |
| 5 | 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`. |
| 6 | 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. |
| 7 | |
| 8 | Don't invent facts the note doesn't contain. Bring your own voice; this drafts the structure. |
| 9 | |
| 10 | ## Depth |
| 11 | - quick: the follow-up message only. |
| 12 | - standard: debrief notes + the message + a subject line. |
| 13 | - deep: + a second nudge for if they go quiet, with the date to send it. |