---

name: briefing-generator description: Generate comprehensive daily briefings by orchestrating data from calendar, email, Teams, and Wrike into a Notion page. Triggers on "Generate my daily briefing", "Create today's briefing", "What's on my schedule today?" (comprehensive view), or "Give me my daily briefing for [date]". Do NOT trigger for simple calendar/email queries - use this only for full briefing generation.

Daily Briefing Orchestrator

Generate complete daily briefings by executing a 6-step pipeline that creates a Notion entry and populates it with data from all connected sources.

Pipeline Sequence

Execute these steps in order. Steps 2-5 are optional and non-fatal if they fail.

Input Parameters

Copyinterface DailyBriefingInput {
  date?: string;        // YYYY-MM-DD format (default: today)
  skip_calendar?: boolean;
  skip_email?: boolean;
  skip_teams?: boolean;
  skip_wrike?: boolean;
}

Validation:

• Date format: YYYY-MM-DD
• Max future date: 7 days
• Default: Today's date

Execution Workflow

1. Validate Input

• Validate date format (YYYY-MM-DD)
• Check date is not >7 days in future
• Default to today if not provided

2. Execute Pipeline

For each step:

1. Update user with progress: [X%] Step description...
2. Execute the step
3. On success: Mark complete, continue
4. On failure:
   • Critical (Step 1): Stop pipeline, return error
   • Non-critical (Steps 2-6): Log warning, continue

Progress format:

Copy[17%] Creating briefing entry... ✅ (3.2s)
[33%] Fetching calendar events... ✅ (12.1s)
[50%] Summarizing emails... ✅ (15.3s)
[67%] Extracting Teams action items... ✅ (18.7s)
[83%] Fetching Wrike tasks... ✅ (12.4s)
[100%] Generating summary... ✅ (7.9s)

3. Return Results

Success criteria: Entry created + at least 1 data source collected

Step Implementation Details

Step 1: Create Notion Entry (CRITICAL)

• Create entry in Daily Briefing database (ID: b063f8ee870e4caa956b1e1e24da31cf)
• Set Phase to "1-Email"
• Set Status to "In Progress"
• Retry once on failure (5s delay)
• If fails: Stop entire pipeline

Steps 2-5: Data Collection

Calendar (Step 2):

• Fetch today's events from Google Calendar
• Calculate deep work blocks
• Update "Today's Schedule" section in Notion

Email (Step 3):

• Search recent emails (last 24h) from Gmail/M365
• Identify action-required items
• Update "Email Summary" section

Teams (Step 4):

• Search chats/channels for action items
• Extract @mentions and requests
• Update "Teams Action Items" section

Wrike (Step 5):

• CRITICAL: Fetch workflows FIRST to map customStatusId to status names
• Get tasks due today/overdue
• Get tasks assigned to user
• Update "Wrike Tasks" section

Step 6: Generate Summary

• Consolidate all collected data
• Identify top 3 priorities
• Flag urgent/overdue items
• Set Status to "Ready"

Error Handling

See references/error-handling.md for complete recovery strategies.

Output Format

Success Response:

Copy✨ **Your Daily Briefing is Ready!**

📅 **Date:** [formatted date]

**View Your Briefing:** [Notion URL]

---

📊 **Quick Overview:**
- **Meetings Today:** X (Deep work: X hours)
- **Unread Emails:** X (X requiring action)
- **Teams Action Items:** X (X urgent ⚠️)
- **Active Wrike Tasks:** X (X overdue ⚠️)

⚠️ **Top 3 Priorities:**
1. [Priority 1]
2. [Priority 2]
3. [Priority 3]

---

**Generated in X seconds**

Partial Success: Same format but note which sources failed with ⚠️.

Critical Failure: Show error code, details, and recommended actions.

Performance

• Expected time: 60-90 seconds
• Total API calls: ~50-60
• Step 1 can be retried once (5s delay)

Configuration

Copyconst CONFIG = {
  max_future_days: 7,
  max_execution_time_seconds: 180,
  max_failed_optional_steps: 3,
  critical_step_retry_count: 1,
  critical_step_retry_delay_seconds: 5
};