# Followup

> Draft the single follow-up to an unanswered cold email, or draft the reply to a company that has responded. Use when a follow-up comes due, when a reply arrives, or to see across both trackers what is owed. Enforces the one-follow-up-only rule.

- Skill: `faaz17/followup` (Agent Skill)
- Install (CLI): `npx skillmds@latest add faaz17/followup`
- Raw SKILL.md: https://api.skillmd.com/api/skills/faaz17/followup/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Productivity
- Author: Faaz17 (https://skillmd.com/u/faaz17)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/faaz17/followup

---


# /followup, the one nudge and the replies

Usage: `/followup` (everything due) · `/followup "<Person Name>" Space42` · `/followup --replies`

## Steps

1. **Read both trackers and both `sent/` folders.** The folders are ground truth; the tracker is the summary. When they disagree, fix the tracker.

2. **Spawn `followup_planner`** to compute what is due against today.

3. **Handle replies before anything else.** A reply is worth more than a week of cold outreach. If one is waiting, draft that answer first.

4. **For each follow-up due (day 6–7, no reply):**
   - Confirm no follow-up has already gone. If one has, the answer is `no-reply` and the company is finished for this cycle. There is no second nudge
   - Draft it: under 60 words, `Re:` plus the exact original subject so it threads, the single strongest link restated, the referral fallback, no attachment, no new argument
   - Save to `<person>/sent/YYYY-MM-DD-<company>-followup.md`, status `ready`
   - Run `send_qa` on it

5. **For each reply:**

   | Reply | Response |
   |---|---|
   | Interested, wants a call | Confirm within 24 hours. Offer concrete times. Attach the CV now |
   | Asks for the CV or portfolio | Send it. At most two files. Never a company its own recommendation letter |
   | "Not this cycle" | Short thanks, ask when to check back, park it with a diary date |
   | Rejection | Short thanks, plus the one question: is there someone else worth talking to. This converts |
   | Forwarded internally | Thank them, and treat the new person as a warm contact rather than a cold one |
   | Out of office | No action. Push the follow-up date to after their return |

6. **Close out anything past day 14** with no reply after a follow-up: status `no-reply`. Do not re-contact for three weeks, and then only a different person.

7. **Push outcomes to the vault.** A replying contact becomes a `04 People/` note via `/obsidian-person` — name, company, role, context, and no contact details. An interview becomes a line in `09 Reference/Planned Events.md`.

8. **Update both trackers.**

## Output format

```
## Follow-up run — <date>

### Drafted
| Person | Company | Type | Words | Status |
|---|---|---|---|---|

### Replies needing an answer
| Person | Company | What they said | Waiting | Drafted? |
|---|---|---|---|---|

### Closed out
| Person | Company | Reason | Status |
|---|---|---|---|

### Due later
| Person | Company | Due |
|---|---|---|

## Next action
<one thing>
```

## Rules

- **One follow-up per company, ever.** The single rule most likely to be broken with good intentions. A second nudge converts almost nothing and turns a neutral non-answer into a bad impression.
- Follow-ups stay under 60 words and add no new argument. If the first email did not work, a longer second one will not either.
- Never chase a reply less than 24 hours old.
- Avoid Friday afternoons and weekends. Tuesday to Thursday morning gets opened. The UAE week runs Monday to Friday, so a Sunday send lands before anyone is reading.
- Never send. Drafts go to the folder for a human.
- Keep both trackers in step. Updating one and not the other leaves the next session with a wrong picture.