外联状态

---
name: outreach-status
description: 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".
---

# /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>)
Dossiers written: <n>
Contacts verified: <n> of <n>

### Notes vs reality
<discrepancies, or "consistent">

### Blocked on
<what, and who has to unblock it>

## Next action (do this literally next)
<one concrete step>
```

## Rules

- One next action, not five.
- Respect phase discipline. Never suggest a Phase N+1 task while Phase N's deliverable does not exist.
- If PROJECT_NOTES says a phase is done and the deliverable is not on disk, the phase is not done. Say it.
- Never report a contact as verified when the tracker says `pattern` or `unverified`.
- Report reply rates as they are. A zero reply rate after ten sends is information about the angle, and hiding it wastes the next ten.
- **Senders in different fields do not share a target list.** Never report one sender's state against another's targets. While a sender still has open questions in their `profile.md`, lead with those.