$npx -y skills add chacosoldier/compabob --skill post-callCapture a debrief right after a meeting or call — what was decided, what was committed, and what changed. Use for "/post-call", "debrief the call with X", or "I just got off a call with Y".
| 1 | # Post-Call Debrief |
| 2 | |
| 3 | Close the loop that `/meeting-prep` opens. Turn a finished conversation into durable vault state. |
| 4 | |
| 5 | ## Steps |
| 6 | |
| 7 | 1. **Gather.** Ask the user for the raw account of the call, or work from notes or a transcript they provide. |
| 8 | 2. **Extract** four things: |
| 9 | - **Decisions** — what was actually decided. |
| 10 | - **Action items** — who owes what, by when. Run these through the `second-brain` task intake gate so they do not duplicate existing tasks. |
| 11 | - **New information** — anything that changes what the vault knows about a person, account, or project. |
| 12 | - **Follow-up** — the next touchpoint, if any. |
| 13 | 3. **Update the vault.** |
| 14 | - Write or update the meeting note `vault/Meetings/YYYY-MM-DD-<slug>.md`. |
| 15 | - Update each attendee's `vault/People/<Name>.md`: append to `## Interactions`, refresh their current focus. |
| 16 | - Update the relevant project or pipeline note. |
| 17 | 4. **Confirm** the changes with the user before writing anything that overwrites existing content. |
| 18 | |
| 19 | ## Output |
| 20 | |
| 21 | A short summary first: the one decision or change that matters most. Then the meeting note content for review. Then the list of vault files that will be created or updated, for approval. |