outreach-statuslisted

Report where the internship outreach stands for one or both people — what is sent, awaiting reply, due for follow-up, and the literal next action. Use when starting a session cold, or when asked "where are we" or "what's next".
Faaz17/Agents-and-Skills · ★ 1 · AI & Automation · score 74

Install: claude install-skill Faaz17/Agents-and-Skills

# /outreach-status, the honest snapshot Usage: `/outreach-status` (both) · `/outreach-status "<Person Name>"` Fast and honest. No encouragement, no padding. ## Steps 1. **Read `.claude/PROJECT_NOTES.md`** — the phase tracker and next action are the stated position. 2. **Check the stated position against what is on disk.** Notes drift and stale notes mislead the next session: - Does `<person>/cv/` actually contain a CV, or is the profile still running on vault data? - Does `profile.md` still contain `TBD`? - How many files are actually in `drafts/` versus `sent/`? - Does `shared/companies/` have real dossiers or empty stubs? - Does `shared/targets.md` have real companies or only the seed list? - Do the tracker rows match the files in `sent/`? 3. **Say so explicitly where they disagree.** If PROJECT_NOTES claims Phase 3 and `shared/companies/` is empty, the project is in Phase 2. 4. **Compute what is due** — spawn `followup_planner` if anything has been sent. 5. **Report per person, then the shared state.** 6. **Give exactly one next action.** The plan lists everything; this skill picks the next thing. ## Output format ``` ## Outreach status — <date> ### Phase: <n, name> (<on track | behind | blocked>) ### <Person Name> Profile: complete | TBD in <fields> Sent: <n> · Awaiting reply: <n> · Replied: <n> · No-reply: <n> Follow-ups due: <n> In drafts: <n> (<statuses>) ### <Second Person> <same> ### Shared Targets: <n> (T1 <n> / T2 <n> / T3 <n>) Doss