daily-prep
Compare original and translation side by side
🇺🇸
Original
English🇨🇳
Translation
ChineseDaily 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
- 工作日结束时：「帮我准备明天的日程」
- 任意时间：「帮我准备周五的日程」或者「3月25日的安排是怎样的？」
- 每周规划：运行多日的准备流程
Procedure
操作流程
1. Determine Target Date
1. 确定目标日期
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如果用户指定了日期，就使用指定日期。否则默认使用明日（当前日期+1天）。
如果明日是周六，默认使用下周一；如果明日是周日，默认使用下周一。
计算输出路径：
outputs/YYYY/MM/YYYY-MM-DD-prep.html2. Pull Calendar via WorkIQ
2. 通过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?"
使用WorkIQ MCP工具获取日历数据，向WorkIQ发起查询：
「我在{目标日期}有哪些会议？请为每个会议返回以下信息：主题、开始时间、结束时间、组织者、所有参会者及其邮箱地址、地点、是否为线上会议，以及我是否接受/拒绝了邀请。」
如果返回的信息不足，发起二次查询：
「{目标日期}的会议中，哪些被标记为可选或暂定？哪些是重复会议？」
3. Classify Each Meeting
3. 对每个会议进行分类
Apply these labels based on attendee domains and subject:
| Label | Criteria |
|---|---|
| External attendees from customer/partner domains, or subject matches a known customer name |
| Only internal company domain attendees |
| CoP, community, guild, learning sessions |
| Training, workshop, certification, learning |
| Tentative, low importance, or known recurring optional (e.g., "Office Hours", "Open Q&A") |
| Private events, non-work |
根据参会者域名和会议主题，应用以下标签：
| 标签 | 判定标准 |
|---|---|
| 有来自客户/合作伙伴域名的外部参会者，或者主题匹配已知的客户名称 |
| 仅包含公司内部域名的参会者 |
| 实践社群、社区、行业协会、学习类会议 |
| 培训、工作坊、认证、学习相关会议 |
| 暂定状态、低优先级，或者已知的可选重复会议（例如「开放办公时间」、「公开答疑」） |
| 私人事件，非工作相关 |
Zone Markers
时段标记
For every meeting, check the organizer field and apply these additional markers:
| Condition | Marker | Action |
|---|---|---|
| Starts ≥ 15:30 and < 16:00 (any organizer) | | Recommend decline |
| Starts ≥ 16:00 and not self-organized | | Recommend decline |
| Starts ≥ 16:00 and self-organized | (no flag) | OK — you chose to schedule it |
| Before 09:00 and not self-organized | | Recommend decline — intrudes on learning window |
| Before 09:00 and self-organized | (no flag) | OK — you chose to schedule it |
| Overlaps 12:00–13:00 | | Note in Calendar Notes |
"Self-organized" means you are the meeting organizer (check the organizer field from WorkIQ).
为每个会议检查组织者字段，添加以下额外标记：
| 条件 | 标记 | 操作建议 |
|---|---|---|
| 开始时间 ≥15:30 且 <16:00（任意组织者） | | 建议拒绝 |
| 开始时间 ≥16:00 且非自行组织 | | 建议拒绝 |
| 开始时间 ≥16:00 且自行组织 | （无标记） | 正常 —— 是你主动安排的会议 |
| 开始时间 <09:00 且非自行组织 | | 建议拒绝 —— 占用了学习窗口 |
| 开始时间 <09:00 且自行组织 | （无标记） | 正常 —— 是你主动安排的会议 |
| 时间与12:00–13:00重叠 | | 在日程备注中说明 |
「自行组织」指你本人是会议组织者（可从WorkIQ返回的组织者字段校验）。
4. Ideal Day Structure
4. 理想日程结构
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.
| Zone | Time | Purpose | Rules |
|---|---|---|---|
| Morning Focus | Before 09:00 | Admin, learning, personal work | Protect from others' meetings. Flag external events. |
| Customer Zone | 09:00–12:00 | Customer / external meetings | Max 2 customer meetings. Prefer mornings for external calls. |
| Lunch | 12:00–13:00 | Break | Protected. Flag any overlap. |
| Deep Work | 13:00–15:30 | Deliverables, focused coding/writing | Minimize meetings. Flag non-essential meetings as deep work disruption. |
| Protected (strict) | 15:30–16:00 | End of day wind-down | Flag all meetings regardless of organizer. |
| Protected (flex) | 16:00+ | End of day | Flag others' meetings only. Self-organized OK. |
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)
将以下结构作为所有分析步骤的决策框架，每个会议都需要对照这些时段进行评估。用户可以根据个人作息调整这些时间和目标。
| 时段 | 时间 | 用途 | 规则 |
|---|---|---|---|
| 晨间专注 | 09:00之前 | 行政事务、学习、个人工作 | 避免被他人安排的会议占用，标记外部事件 |
| 客户对接区 | 09:00–12:00 | 客户/外部会议 | 最多安排2场客户会议，优先将外部通话安排在上午 |
| 午餐 | 12:00–13:00 | 休息 | 受保护时段，标记所有重叠的会议 |
| 深度工作 | 13:00–15:30 | 交付物产出、专注编码/写作 | 尽量减少会议，标记非必要会议为深度工作干扰项 |
| 严格保护 | 15:30–16:00 | 工作日收尾 | 不管组织者是谁，标记所有该时段的会议 |
| 灵活保护 | 16:00之后 | 工作日结束 | 仅标记他人安排的会议，自行组织的会议不受限制 |
每日目标：
- 学习时长：1.5小时（来自晨间专注时段+间隙时间）
- 深度工作时长：2.5小时（来自13:00–15:30时段）
- 客户会议：最多2场（优先安排在09:00–12:00）
5. Detect Conflicts & Day Fit Issues
5. 检测冲突和日程适配问题
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):
| Check | Condition | Flag |
|---|---|---|
| Customer overload | >2 | Flag 3rd+ as "Consider rescheduling to another day" |
| Deep work disruption | Non-essential meetings in 13:00–15:30 zone | "Disrupts deep work — consider moving to morning" |
| Non-ideal placement | Customer meetings outside 09:00–12:00 | "Customer meeting outside preferred morning zone" |
| Early intrusion | Others' meetings before 09:00 | "Intrudes on learning window — recommend decline" |
| Lunch conflict | Meeting overlaps 12:00–13:00 | "Conflicts with lunch break" |
对比事件的时间窗口，在冲突表格中标记时间重叠的会议并给出对应建议 —— 客户会议优先级高于内部/可选会议。
同时检测以下日程适配问题（在单独的「日程适配问题」表格中上报）：
| 检查项 | 条件 | 标记 |
|---|---|---|
| 客户会议过载 | 超过2场 | 将第3场及以上标记为「建议改期到其他日期」 |
| 深度工作被干扰 | 13:00–15:30时段有非必要会议 | 「干扰深度工作 —— 建议改到上午」 |
| 时段安排不合理 | 客户会议安排在09:00–12:00之外的时段 | 「客户会议未安排在优先的上午时段」 |
| 过早占用时段 | 09:00之前有他人安排的会议 | 「占用学习窗口 —— 建议拒绝」 |
| 午餐冲突 | 会议与12:00–13:00重叠 | 「与午休时间冲突」 |
6. Gather Context from Workspace
6. 从工作区收集上下文
- Read open task files for tasks related to customer names or attendees in tomorrow's meetings
- Search workspace folders for recent files related to those customers or topics
- Check recent meeting summaries or plans for relevant prep context
- Use this to generate actionable prep bullets per meeting
- 读取与明日会议中的客户名称或参会者相关的未完成任务文件
- 在工作区文件夹中搜索与这些客户或主题相关的近期文件
- 查看近期的会议纪要或计划，获取相关的准备上下文
- 基于以上信息为每个会议生成可执行的准备要点
7. Generate Prep per Meeting
7. 为每个会议生成准备内容
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
按时间顺序为每个会议提供以下内容：
- 时间、主题、组织者
- 参会者列表（姓名，外部参会者标注所属公司）
- 基于未完成任务、近期纪要和会议主题生成的3-5条可执行准备要点
- 如果没有可用上下文，标注会议中需要提问/澄清的内容
8. Find Learning & Focus Slots
8. 查找学习和专注时段
After generating prep per meeting, analyze the day's schedule to find open slots:
-
Morning Focus confirmation — Verify the morning focus window is clear. If any non-self-organized event exists there, flag it.
-
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.
-
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.
-
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")
为每个会议生成准备内容后，分析当日日程找到空闲时段：
-
晨间专注确认 —— 校验晨间专注窗口是否为空，如果有非自行组织的会议则进行标记。
-
学习时段 —— 找到晨间窗口中≥30分钟的间隙，以及其他适合技能提升的空闲时段，目标：每天1.5小时。为每个时段标注：时间范围、时长、建议活动。
-
深度工作块 —— 找到13:00–15:30时段中连续的空闲间隙用于产出交付物。为每个时间段标注：时间范围、时长、从待办任务中推荐的对应任务。
-
上报总计数据：
- 找到的学习时长与1.5小时目标的对比（例如「1.0小时 / 1.5小时目标 —— 差0.5小时」）
- 13:00–15:30时段可用的深度工作时长（例如「2.0小时 / 2.5小时可用」）
9. Productivity Recommendations
9. 生产力建议
Analyze the full day and provide:
| Section | What to Include |
|---|---|
| Day Fit Score | Rate 0–100% how well the day matches the Ideal Day Structure. Criteria: (1) morning focus clear (+20%), (2) ≤2 customer meetings in 09:00–12:00 (+20%), (3) lunch 12:00–13:00 protected (+15%), (4) deep work 13:00–15:30 intact (+20%), (5) nothing after 15:30 or only self-organized after 16:00 (+15%), (6) ≥1h learning slots found (+10%). Show as: 🟢 ≥80%, 🟡 50–79%, 🔴 <50%. |
| Day Shape | Total meeting hours, focus time available, learning hours, deep work hours, heavy/moderate/light assessment |
| Decline Candidates | Auto-include: (1) all meetings 15:30–16:00, (2) others' meetings ≥16:00, (3) others' meetings <09:00, (4) 3rd+ customer meeting, (5) optional meetings during deep work zone. Show "Reclaim" column with minutes recovered. Self-organized meetings before 09:00 or after 16:00 are excluded from auto-decline. |
| Conflict Resolution | Specific recommendation for each overlap |
| Learning Slots | Gaps for upskilling — from Step 8. Table: Window, Duration, Suggested Activity. Show total vs. 1.5h target. |
| Deep Work Blocks | Free gaps in 13:00–15:30 for deliverables — from Step 8. Table: Window, Duration, Suggested Task. |
| Energy Management | Flag if >3h back-to-back customer meetings without a break |
| Top 3 Priorities | The 3 most impactful things to accomplish (meetings + tasks combined) |
分析完整日程，提供以下内容：
| 板块 | 包含内容 |
|---|---|
| 日程适配得分 | 按0-100%评估当日日程与理想日程结构的匹配度。评分标准：(1) 晨间专注窗口为空 (+20%)，(2) 09:00–12:00时段客户会议≤2场 (+20%)，(3) 12:00–13:00午休时段不受干扰 (+15%)，(4) 13:00–15:30深度工作时段完整 (+20%)，(5) 15:30之后无会议，或16:00之后仅有自行组织的会议 (+15%)，(6) 找到≥1小时的学习时段 (+10%)。展示规则：🟢 ≥80%，🟡 50–79%，🔴 <50%。 |
| 日程构成 | 总会议时长、可用专注时长、学习时长、深度工作时长，以及日程强度评估（高强度/中等强度/低强度） |
| 建议拒绝的会议 | 自动包含：(1) 所有15:30–16:00的会议，(2) 16:00之后他人安排的会议，(3) 09:00之前他人安排的会议，(4) 第3场及以上的客户会议，(5) 深度工作时段的可选会议。新增「回收时长」列标注拒绝后可恢复的时长。09:00之前或16:00之后自行组织的会议不纳入自动拒绝列表。 |
| 冲突解决建议 | 为每个时间重叠的情况提供具体的解决建议 |
| 学习时段 | 可用于技能提升的间隙 —— 来自步骤8，表格包含：时间窗口、时长、建议活动，展示总时长与1.5小时目标的对比。 |
| 深度工作块 | 13:00–15:30时段可用于产出交付物的空闲间隙 —— 来自步骤8，表格包含：时间窗口、时长、建议任务。 |
| 精力管理建议 | 如果有超过3小时无休息的连续客户会议则进行标记 |
| Top 3优先级事项 | 当日最有价值的3项待完成事项（包含会议+任务） |
10. Write the File
10. 写入文件
Create the output file at as a self-contained HTML file with embedded CSS (dark theme, color-coded timeline, responsive layout).
outputs/YYYY/MM/YYYY-MM-DD-prep.htmlIf a file already exists for that date, read it first and update rather than overwrite — the user may have added manual notes.
在路径下创建输出文件，为自包含的HTML文件，内置CSS（深色主题、彩色时间线、响应式布局）。
outputs/YYYY/MM/YYYY-MM-DD-prep.html如果对应日期的文件已存在，先读取已有内容再更新而不是直接覆盖 —— 用户可能已经添加了手动备注。
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"
- 「帮我准备明天的日程」
- 「周五的安排是怎样的？」
- 「3月28日的每日准备」
- 「帮我准备下周一的日程 —— 重点关注客户会议」
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
- 必须有可用的WorkIQ MCP工具用于访问日历（Microsoft 365 / Outlook）
- 存储有待办任务文件和客户/项目文件夹的工作区，用于上下文补充
- 输出为自包含HTML文件 —— 无外部依赖