/thank-you

Usage: /thank-you <job folder or company + role> (or just ask in plain English).

1. Debrief the user with quick questions (one at a time, skip what they volunteer): who they met (names, titles, emails if they have them); what each person talked about; one thing they connected with per person; questions they struggled with; next steps and timeline the employer gave; their gut feeling. If a meeting-notes app is connected, ask once whether to read the user's own notes from this interview first; a transcript of a call with others only on their explicit OK (knowledge/data-connectors.md).
2. Save interviews/<YYYY-MM-DD>-<job folder>-debrief.md (the interview's date and the job's folder name) with the user's answers and lessons (what to fix next time). If that file already exists, ask whether this is the same interview: if yes, add to it; if not (a second round the same day), use -2, -3 so an earlier debrief is never overwritten.
3. Draft one thank-you per interviewer into outbox/ (email, ≤ 120 words, sent within 24 hours): thank them, reference one specific thing from that conversation, connect it to one real thing the user did, and end with a specific forward-looking line (not "I'd love to join your team"). If the user fumbled a question with this person, add one or two sentences with a clearer answer built only from what they really know. No groveling, no re-pitching everything. Subject: "Thank you, <role> interview". Notes to people on the same panel must differ in more than the name; interviewers often compare them. If the user asks whether notes matter: a note rarely decides the outcome, but some interviewers notice when one is missing, so it's cheap insurance. Keep it short and sent the same day or the next morning. If the user has no email for someone, ask the recruiter to pass the note along (or send one combined note through the recruiter). A LinkedIn note is the last resort (channel: linkedin): a connection note on a free account is capped at 200 characters (and free accounts get only a few personalized invites a month), or send a normal message if they're already connected. Also thank the recruiter who coordinated. For a one-way recorded interview there's no interviewer: send one short note to the recruiter, or skip it.
4. Run truth-checker, then voice-editor. Tell the user the drafts are in /outbox. 4a. If the user is exploring (profile/life-design.md has a direction this job belongs to, or they're unsure whether this kind of work fits): end the debrief with the four reflection questions, one per message: what energized you, what challenged you, what you discovered, what you might try next. Save the answers in the debrief file, and offer to add a line under "Experiments" in profile/life-design.md (/explore).
5. Tracker: re-read the row first. If it already holds a later booked step (another Interview <date>, a Take-home due <date>, Respond to offer, or an Also: item at the start of notes), keep it (promote the Also: item if this interview was the next_action; the playbook's "Two commitments at once"). Only when nothing else is booked: next_action=Wait for decision, next_action_date = the date they said, +1 business day (or +7 business days after the interview date if unknown). Add interviewers to contacts/contacts.csv (relationship=hiring-manager, recruiter, or interviewer; status=talked, touches=0); for someone already there, never lower their status (keep referred). Log the changes in history/activity.md. The thank-you notes don't change follow-up dates (the job row owns them), and once sent they set last_contact only: a thank-you to someone at talked or referred adds no touches and no next_followup.