followuplisted

# /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 th