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

GitHub

/follow-up

  1. Read jobs/tracker.csv and contacts/contacts.csv. Due = a job at applied, screening or interviewing whose next_action is Follow up… or Wait for decision and whose next_action_date ≤ today; or a contact (not cold) whose next_followup ≤ today. Skip a contact's date when their job is at applied or 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 in knowledge/job-search-playbook.md ("Follow-up cadence").
  2. 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 /apply now: 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 them cold and moving on (the /contacts board shows "stop here" and offers Mark cold).
    • Applications: count only actual follow-ups (followups in 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 as ghosted and moving on.
  3. 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.md or profile/story-bank.md; never invent a project update. Save each as its own file in outbox/ (job: set). Run truth-checker, then voice-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_to set). 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 (followups in the tracker), then recommend moving on.
  4. 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-inbox finds 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 to followups, then either set next_action=Follow up a week later (only where the playbook allows another nudge: after an interview, or a named person has replied) or next_action=Wait for decision about 2 weeks out (if still nothing then, offer to close it as ghosted). For pure networking, set the contact's next_followup to 5 business days after the send, or blank once touches reaches 2. Thank-yous and updates to someone at replied, talked or referred set last_contact only (no touches, no next_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 in history/activity.md.
  5. Tell the user how many drafts are waiting and to open /outbox. Mention they can press "Message sent…" on /contacts for 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/ (draft or in-gmail-drafts, any date); a file in outbox/sent/ whose sent: date is on or after the item's current due date (next_action_date, or the contact's next_followup), which means it was sent but the tracker hasn't caught up; or a file in outbox/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 (recommend cold or ghosted), 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.csv or contacts/contacts.csv (step 4 waits until the user actually sends).
  • Log: follow-up drafts · <N> drafts in the Outbox, or follow-up drafts · nothing due. Summary: how many drafts, for which companies, and what needs the user (a name to find, a job to close).