[Admin Assistant] Task 2: Scheduled Briefings (Morning, Midday, EOD)

[jsirish]

Overview

Create automated briefing system for morning, midday, and end-of-day summaries.

Requirements

Morning Briefing (8:05 AM Weekdays)

Delivery: Telegram + Email (optional)

Content:

☀️ Good Morning! Here's your briefing for [Date]

🌤️ Weather: [Current conditions, high/low, precipitation]

📅 Today's Calendar:
- [Time] Meeting 1 (location/link, attendees)
- [Time] Meeting 2 (prep notes if available)
- ...

✅ Tasks Due Today:
- [Task 1] - Project X
- [Task 2] - Client Y
- Overdue: [Any overdue items]

💼 HubSpot Deals Needing Attention:
- [Deal 1] - Closing [date] - [amount]
- [Deal 2] - Stale [X] days

🤖 AutoPipe Pipeline:
- Issues in review: [count]
- PRs awaiting approval: [count]
- Blocked items: [list]

📧 Inbox Summary:
- AgentMail: [X] new
- Gmail urgent: [Y] items

⚠️ Action Items:
- [Any urgent items requiring immediate attention]

Midday Check-in (12:00 PM Weekdays)

Content:

• Morning meeting recap (if any)
• Afternoon calendar preview
• Task progress update
• Any new urgent items

End-of-Day Summary (5:00 PM Weekdays)

Content:

🌆 End of Day Summary — [Date]

✅ Completed Today:
- [List from task system]
- [Meetings attended]

📋 Tomorrow's Preview:
- [First 3 meetings]
- [Tasks due tomorrow]
- [Deadlines approaching]

⚠️ Blockers/Concerns:
- [Any issues to address]

📊 Business Metrics:
- Deals closed this week
- Pipeline health
- Response times

Configuration

briefings:
  morning:
    enabled: true
    time: "08:05"
    timezone: "America/Chicago"
    weekdays: true
    channels: [telegram, email]
  midday:
    enabled: true
    time: "12:00"
    channels: [telegram]
  evening:
    enabled: true
    time: "17:00"
    channels: [telegram, email]

Deliverables

• Morning briefing cron job
• Midday check-in cron job
• Evening summary cron job
• Template system for briefings
• Data aggregation logic
• Telegram delivery
• Email delivery (optional)

Acceptance Criteria

• Briefings delivered on time
• All data sources included
• Formatting clean and readable
• No duplicate information
• Action items highlighted
• Delivery channels work

Technical Notes

• Use OpenClaw cron with sessions_spawn
• Aggregate data from multiple sources
• Keep under 2-minute read time
• Use emojis for visual scanning
• Cache data to avoid repeated API calls

Relates to #182