log-outreachlisted

# /log-outreach, close the session Usage: `/log-outreach` The next session reads `PROJECT_NOTES.md` first. Whatever this skill writes is what the next session believes, so it has to be true. ## Steps 1. **Reconcile the trackers against disk.** For each person, compare `tracker.md` against the files in `drafts/` and `sent/`. The files win. Fix the tracker where they disagree, and note what was out of step — a recurring mismatch means a step in the workflow is being skipped. 2. **Update statuses.** Every draft has a `status` in its frontmatter that says exactly what still has to happen to it. Never end a session with a file in an unclear state. 3. **Set follow-up dates.** Anything sent this session gets `followup_due` at +6 days, in the frontmatter and the tracker. 4. **Update `PROJECT_NOTES.md`:** - The phase, and honestly — a phase whose deliverable does not exist is not done - What is blocked, and who unblocks it - What is still undecided - **One** next action - A new row in the session log: date, and what actually happened 5. **Push the vault-worthy parts.** Not everything belongs in the vault; this repo holds the operational detail. The vault gets: - A dev-log note in `10 Logs/` for a substantial session → `/obsidian-log` - A person note in `04 People/` for anyone who replied → `/obsidian-person`. Name, company, role, context. **No email address, no phone number** - An interview or call → one line in `09 Reference/Planned Events.md` - A d