call-recap-follow-uplisted

# Call Recap and Follow-Up A recorded call is not one email. It is a set of them, sitting with different people, blocked on each other in a specific order. This skill turns a recording into that whole set, plus the read on the call that makes the emails worth sending. The failure mode this exists to prevent: writing a tidy recap to the coordinator, feeling done, and leaving the three emails that actually move the account unwritten. --- ## What this needs **Minimum: a transcript.** Pasted, uploaded, or pointed at. Everything below still runs, and the output arrives in chat. **Better with** a connected meeting recorder, which fetches the transcript itself; a connected mailbox, which finds real addresses and the threads to reply into; and somewhere to write files, which keeps the drafts document next to the account. **Best with** a workspace holding account notes and a voice guide. That is what turns a competent recap into one the user sends without rewriting it. Nothing here is required. Each missing piece costs one specific capability, and the skill says which one out loud rather than guessing around it. --- ## Step 0: Orient Check what context exists before touching the recording. None of it is a prerequisite. 1. House rules, if the workspace keeps them - a `CLAUDE.md` or equivalent covering workflow and editorial conventions 2. A voice or style guide - how the user writes. Where one exists it is non-negotiable, and it is the difference between a draft they send a