Daily Prep

Daily Prep

Generate a structured prep file for the next working day with meeting details, prep bullets, linked tasks, and productivity recommendations.

When to Use

• End of day: "prepare me for tomorrow"

• Any time: "prep me for Friday" or "what does March 25 look like?"

• Weekly planning: run for multiple days

Procedure

1. Determine Target Date

If the user specifies a date, use it. Otherwise, default to tomorrow (current date + 1 day). If tomorrow is Saturday, default to Monday. If Sunday, default to Monday. Compute the output path: outputs/YYYY/MM/YYYY-MM-DD-prep.html

2. Pull Calendar via WorkIQ

Use the WorkIQ MCP tool to fetch the calendar. Ask WorkIQ:

"What meetings do I have on {target date}? For each meeting, include: subject, start time, end time, organizer, all attendees with their email addresses, location, whether it's online, and whether I've accepted or declined."

If the response is insufficient, make a follow-up query:

"For the meetings on {target date}, which ones are marked as optional or tentative? Which ones are recurring?"

3. Classify Each Meeting

Apply these labels based on attendee domains and subject:

Zone Markers

For every meeting, check the organizer field and apply these additional markers:

"Self-organized" means you are the meeting organizer (check the organizer field from WorkIQ).

4. Ideal Day Structure

Use this as the decision framework for all analysis steps. Every meeting must be evaluated against these zones. Users should adapt these times and targets to their personal routine.

Targets per day:

• Learning hours: 1.5h (from morning focus + gap time)

• Deep work hours: 2.5h (13:00–15:30 zone)

• Customer meetings: max 2 (preferably in 09:00–12:00)

5. Detect Conflicts & Day Fit Issues

Compare event time windows. Flag overlaps in a Conflicts table with a recommendation for each — prioritize customer meetings over internal/optional.

Also detect these day fit issues (report in a separate "Day Fit Issues" table):

6. Gather Context from Workspace

1. Read open task files for tasks related to customer names or attendees in tomorrow's meetings

2. Search workspace folders for recent files related to those customers or topics

3. Check recent meeting summaries or plans for relevant prep context

4. Use this to generate actionable prep bullets per meeting

7. Generate Prep per Meeting

For each meeting (chronological), include:

• Time, subject, organizer

• Attendee list (first name, company if external)

• 3–5 actionable prep bullets based on open tasks, recent summaries, and meeting subject

• If no context available, note what to ask/clarify in the meeting

8. Find Learning & Focus Slots

After generating prep per meeting, analyze the day's schedule to find open slots:

1. Morning Focus confirmation — Verify the morning focus window is clear. If any non-self-organized event exists there, flag it.

2. Learning Slots — Find gaps ≥ 30 min in the morning window and any other free slots suitable for upskilling. Target: 1.5h/day. For each slot: time range, duration, suggested activity.

3. Deep Work Blocks — Find continuous free gaps in the 13:00–15:30 zone for deliverables. For each block: time range, duration, suggested task from open tasks.

4. Report totals:

   • Learning hours found vs. 1.5h target (e.g., "1.0h / 1.5h target — 0.5h short")

   • Deep work hours available in 13:00–15:30 (e.g., "2.0h / 2.5h available")

9. Productivity Recommendations

Analyze the full day and provide:

10. Write the File

Create the output file at outputs/YYYY/MM/YYYY-MM-DD-prep.html as a self-contained HTML file with embedded CSS (dark theme, color-coded timeline, responsive layout).

If a file already exists for that date, read it first and update rather than overwrite — the user may have added manual notes.

Example Prompts

• "Prepare me for tomorrow"

• "What does Friday look like?"

• "Daily prep for March 28"

• "Prep me for next Monday — focus on customer meetings"

Requirements

• WorkIQ MCP tool must be available for calendar access (Microsoft 365 / Outlook)

• A workspace with task files and customer/project folders for context enrichment

• Output is self-contained HTML — no external dependencies