follow-up
Find every application and contact whose follow-up is due and draft the messages into the Outbox. Use when the user asks about follow-ups, says they haven't heard back, or /today shows items due.
SKILL.md.claude/skills/follow-up/SKILL.md
GitHub/follow-up
- Read
jobs/tracker.csvandcontacts/contacts.csv. Due = a job atapplied,screeningorinterviewingwhosenext_actionisFollow up…orWait for decisionand whosenext_action_date≤ today; or a contact (notcold) whosenext_followup≤ today. Skip a contact's date when theirjobis atappliedor later (the job row owns that follow-up; offer to clear the stale contact date), and never draft two messages for the same person, job and purpose. Other due steps (prep, deadlines) belong to/today. Use the cadence inknowledge/job-search-playbook.md("Follow-up cadence"). - For each due item (max 5 at a time: post-interview checks first, then oldest first; if more are due, say how many and offer the next batch), decide:
- Applied, no reply → short check-in to the contact saved for that job (or the recruiter on the posting). If the posting lists a recruiting email, use that. If there's still nobody, do the "find one human" step from
/applynow: give the user 2–3 quick ways to find a name (LinkedIn search terms, the company's recruiting page, an alum there:.claude/skills/network/references/alumni.md), ask them for the name, and write the draft once they have one. Never save a draft with placeholders like [Name]. - After interview, no news → polite status check referencing the date they gave.
- Networking contact, no reply → one gentle bump, then stop.
- Pure networking with two unanswered touches already (
touches= 2 in contacts.csv) → recommend marking themcoldand moving on (the/contactsboard shows "stop here" and offers Mark cold). - Applications: count only actual follow-ups (
followupsin the tracker, and sent outbox follow-ups), not the first outreach, thank-you notes, scheduling replies or other replies. Before any interview: one follow-up, two only with the playbook's named-person exception. After the latest interview: at most two status checks at the playbook's intervals. Past those limits, recommend closing it asghostedand moving on.
- Applied, no reply → short check-in to the contact saved for that job (or the recruiter on the posting). If the posting lists a recruiting email, use that. If there's still nobody, do the "find one human" step from
- Each draft: ≤ 100 words, references something specific (the role and job ID, the conversation), and ends with an easy yes/no. It may add one small new thing, but only a fact from
profile/master-resume.mdorprofile/story-bank.md; never invent a project update. Save each as its own file inoutbox/(job:set). Runtruth-checker, thenvoice-editor.- Wording: role, job ID and date (applied / interviewed) in the first line; one line of continued interest; one question ("Is there an update on timing?"). Reply in the earlier email thread if there is one (
reply_toset). No guilt-tripping, no bare "just checking in". - Closing an A-priority job as
ghosted: silence often means a stalled role, not a verdict; offer to recheck that company's careers page in about 3 months. - Respect the limits: one follow-up for an online application; a second only if a named person has replied or accepted the user's connection (
followupsin the tracker), then recommend moving on.
- Wording: role, job ID and date (applied / interviewed) in the first line; one line of continued interest; one question ("Is there an update on timing?"). Reply in the earlier email thread if there is one (
- Don't move follow-up dates forward until each draft is actually sent. Then, when the user has sent it (they say so, the Outbox panel reports it, or
sync-inboxfinds it in their Sent mail): follow the playbook rule for when the user sends someone a message. If it was about a job they applied to, the job row owns the date: add 1 tofollowups, then either setnext_action=Follow upa week later (only where the playbook allows another nudge: after an interview, or a named person has replied) ornext_action=Wait for decisionabout 2 weeks out (if still nothing then, offer to close it asghosted). For pure networking, set the contact'snext_followupto 5 business days after the send, or blank oncetouchesreaches 2. Thank-yous and updates to someone atreplied,talkedorreferredsetlast_contactonly (notouches, nonext_followup). Re-read each file right before editing and change only those rows; if the user has the file open in Excel, ask them to save and close it first (playbook, "One writer at a time"). Log each change inhistory/activity.md. - Tell the user how many drafts are waiting and to open
/outbox. Mention they can press "Message sent…" on/contactsfor LinkedIn messages they send by hand.
Scheduled mode (the follow-up drafts routine)
When the instructions say scheduled mode, first read .claude/skills/routines/references/scheduled-mode.md and follow it; it overrides any step above that needs the user.
- Steps 1 to 3, at most 5 drafts. Before each, look for a message to the same person about the same job and purpose, and skip the item if there is one, so a daily run never stacks up repeats: a waiting draft in
outbox/(draftorin-gmail-drafts, any date); a file inoutbox/sent/whosesent:date is on or after the item's current due date (next_action_date, or the contact'snext_followup), which means it was sent but the tracker hasn't caught up; or a file inoutbox/discarded/created on or after that date (the user already said no this round). An older sent follow-up doesn't block the next one: the playbook's second status check a week after the first is drafted once its date comes, within step 2's limits. - Write only new
outbox/draft files (status: draft, never a Gmail draft). No name to write to, a limit reached (recommendcoldorghosted), or anything else that needs a decision: list it, don't draft it. The review is the one combined pass from the shared rules. - Never change
jobs/tracker.csvorcontacts/contacts.csv(step 4 waits until the user actually sends). - Log:
follow-up drafts · <N> drafts in the Outbox, orfollow-up drafts · nothing due. Summary: how many drafts, for which companies, and what needs the user (a name to find, a job to close).