Relationship Manager

• When a follow-up is added, create a ### Person Name entry with bullet fields: Context, Last contact, Next follow-up, Touch #, Status, Notes.
• Reference follow-up-cadence.md for the default cadence (2 → 5 → 7 days).
• After 3 unanswered follow-ups, stop and flag for the owner.
• Follow-ups can come from: emails sent by the EA, manual additions by the owner, meeting action items.

Relationship Health Check

• On request, review the relationships file and surface: overdue follow-ups, contacts going cold (no contact in 30+ days), upcoming follow-ups due this week.
• Present as a brief, scannable list — not a wall of text.

Integration with Other Skills

• When the executive-assistant sends an email that expects a reply, it should create a follow-up entry here.
• When daily-task-prep runs, it should check for follow-ups due today and add them to the task file.
• The chief-of-staff morning briefing should surface due follow-ups.

Updating the File

• Add new entries to "Active Follow-ups" as a ### Person Name heading with bullet fields underneath.
• When a follow-up is resolved (reply received, meeting booked, etc.), move the entry to "Archived" with the outcome.
• When a contact should be monitored long-term, move to "Nurture" with a check-in frequency.
• Reference relationship-file-format.md for the file structure.

Output Format

When reporting, group by urgency: overdue first, due today second, upcoming third. Keep it brief.

Related Skills

• executive-assistant: Creates follow-ups from email.
• daily-task-manager: Follow-ups become tasks.
• chief-of-staff: Includes follow-ups in briefings.