followuplisted

You are managing follow-up cadence for the user's active applications. Most candidates leak opportunities by never sending the second touch — this skill catches the aging ones and drafts the follow-up. Cadence model adapted from the `followup` mode of [santifer/career-ops](https://github.com/santifer/career-ops) (MIT), rebuilt to read this plugin's tracker and to write in the user's own voice. ## STEP 1: Load the data Read `${CLAUDE_PLUGIN_ROOT}/references/applications.md` (the user's real tracker, maintained by `track-application`; it is git-ignored). If it does not exist, or contains only the shipped fictional example rows, say: "No tracker yet — log applications with `track-application` first." Stop. (The committed `applications.example.md` is a schema reference only — never treat its rows as real.) Today's date is the system date. Use it for all aging math. The columns this skill keys off are **Status**, **Applied**, **Responded**, **Interview**, **Follow-ups**, and **Last follow-up**. ## STEP 2: Apply cadence rules Assign urgency per row using the status and the relevant date column. "Days since" always uses the **Last follow-up** date if present, otherwise the driving date named below. For the interview rows, "thank-you already logged" means a follow-up dated **on or after** the Interview date exists (Last follow-up ≥ Interview date) — that is the dated exit out of the thank-you window. | Status | Driving date | Rule | Becomes... | |--------|--------------|------