daily-review

## Purpose Conduct an end-of-day review to capture progress, track what you actually accomplished vs. planned, surface meeting follow-ups, and set up tomorrow. ## Tone Calibration Read `System/user-profile.yaml` → `communication` section and adapt accordingly. --- ## Step 0: Demo Mode Check Check `System/user-profile.yaml` for `demo_mode`. If true, use demo paths. --- ## Step 1: File Discovery Find files modified TODAY: ```bash TODAY=$(date +%Y-%m-%d) find . -type f -name "*.md" -newermt "$TODAY 00:00:00" ! -newermt "$TODAY 23:59:59" 2>/dev/null ``` **Critical rules:** 1. No truncation — list all modified files 2. Today only — use date-based filtering 3. Verify with user — "These are the files I found. What did you actually work on?" --- ## Step 2: Gather Context ### From 03-Tasks/Tasks.md - Tasks completed today (look for `✅ YYYY-MM-DD` matching today) - Tasks started but not finished ### From Weekly Priorities Read `02-Week_Priorities/Week_Priorities.md` for: - This week's strategic focus - How today's work connects to weekly priorities ### From Recent Meetings Check `00-Inbox/Meetings/` for meeting notes from today. ### From ScreenPipe (If Running) **Check if ScreenPipe is available:** ```bash curl -s http://localhost:3030/health | jq -r '.status' 2>/dev/null ``` If ScreenPipe is running, gather automatic activity context: 1. **Time Audit** — Query app usage for today: ``` Use: screenpipe_time_audit(start_time="YYYY-MM-DDT09:00:00", end_time="YYYY-MM-DDT18:00:00") ``` 2. **Activity Summary** — Get narrative of what happened: ``` Use: screenpipe_summarize(start_time="YYYY-MM-DDT09:00:00", end_time="YYYY-MM-DDT18:00:00") ``` 3. **Surface to User:** > "📺 **Screen Activity Summary** (auto-captured): > > **Time breakdown:** > - VS Code: 3.2 hours (41%) > - Slack: 1.5 hours (19%) > - Chrome: 2.1 hours (27%) > - Zoom: 1.0 hour (13%) > > **Activity narrative:** > [Generated summary of the day] > > **Context switches:** 34 (moderate) > **Longest focus session:** 48 minutes > > Does this match your sense of the day?" This provides ground truth for what actually happened vs. what was remembered. ### Commitment Scan (If ScreenPipe Beta Activated & Enabled & Running) **First, check beta activation:** ``` Use: check_beta_enabled(feature="screenpipe") ``` If beta NOT activated, skip this section entirely. **Then check if user has opted in:** Read `System/user-profile.yaml` → `screenpipe.enabled`. If false, skip this section entirely. **If beta activated AND enabled**, scan for uncommitted asks and promises: ``` Use: scan_for_commitments( start_time="YYYY-MM-DDT09:00:00", end_time="YYYY-MM-DDT18:00:00", apps=["Slack", "Gmail", "Teams", "Notion"] ) ``` Then get pending items: ``` Use: get_uncommitted_items(include_dismissed=false) ``` **Surface to user if items found:** > "🔔 **Uncommitted Items Detected** > > ScreenPipe noticed these potential commitments today that don't have matching tasks: > > ### Inbound Asks > > **1. Sarah Chen** (Slack, 2:34 PM) > > "Can you review the pricing proposal by Friday?" > > 📎 Matches: **Q1 Pricing Project** > ⏰ Deadline: Friday > > → [Create task] [Already handled] [Ignore] > > ### Outbound Promises > > **2. You → Tom Baker** (Slack, 4:20 PM) > > "I'll send over the competitive analysis tomorrow" > > 📎 Matches: **Acme Deal** > ⏰ Deadline: Tomorrow > > → [Create task] [Already handled] [Ignore] > > *2 potential commitments detected. 0 have matching tasks.*" For each item the user wants to create as a task: ``` Use: process_commitment(commitment_id="comm-XXXXXX-XXX", action="create_task") Use: create_task(title="...", priority="P2", pillar="...", context="From Slack commitment") ``` For dismissals: ``` Use: process_commitment(commitment_id="comm-XXXXXX-XXX", action="dismiss") ``` --- ## Step 3: Daily Plan Completion Tracking (NEW) **Compare what you planned vs. what you did.** ### 3.1 Find Today's Plan Look for `07-Archives/Plans/YYYY-MM-DD.md` (today's date). ### 3.2 Extract Planned Focus From the "Today's Focus" section, extract the 3 items you planned to focus on. ### 3.3 Track Completion For each planned focus item: - Check if it was completed (look in Tasks.md for completion timestamps) - Check if it was started but not finished - Check if it was blocked or deferred **Surface this:** > "📊 **Daily Plan Completion:** > > You planned 3 focus items this morning: > > 1. ✅ **Prep for Acme meeting** — Complete > 2. 🔄 **Write pricing proposal** — In progress (about 60% done) > 3. ❌ **Reply to Mike** — Didn't get to it > > **Completion rate today:** 1 of 3 (33%) > > What happened with #3? Should it carry to tomorrow?" ### 3.4 Track Over Time (Optional) If tracking completion rates: - Update `System/metrics/daily-completion.md` with today's rate - Surface patterns: "Your average completion rate this week is 67%" --- ## Step 4: Meeting Follow-Up Surfacing (NEW) **For each meeting you had today, surface follow-ups.** ### 4.1 Identify Today's Meetings From calendar or meeting notes, list meetings that happened today. ### 4.2 For Each Meeting, Ask: ``` Use: get_meeting_context(meeting_title="...", attendees=[...]) ``` Then prompt: > "📍 **You met with Sarah Chen today** (Acme Quarterly Review) > > **Any follow-ups to capture?** > - Action items you committed to? > - Things they owe you? > - Decisions that need documentation? > > (Type your follow-ups or 'none')" ### 4.3 Create Follow-Up Tasks For any follow-ups mentioned: - Add to Tasks.md with appropriate priority - Link to the person page - Add due date if mentioned --- ## Step 5: Progress Assessment With user-verified information: - What was accomplished? - What progress was made against weekly priorities? - What got stuck or blocked? - What unexpected things came up? --- ## Step 6: Week Progress Check (Midweek Context) ``` Use: get_week_progress() ``` Show how today's work moved weekly priorities: > "**Week Progress Update:** > > After today, you're at: > - Priority 1: ✅ Complete (finished today!) > - Priority 2: 🔄 60% (moved from 40%) > - Priority 3: ⚠️ Still not started > > You have 2 days left. Tomorrow should focus on Priority 3." --- ## Step 7: Auto-Extract Session Learnings Scan today's conversation for learnings: 1. **Mistakes or corrections** — Did something not work as expected? 2. **Preferences mentioned** — Did you express how you like to work? 3. **Documentation gaps** — Were there questions about how the system works? 4. **Workflow inefficiencies** — Did any task take longer than it should? Write to `System/Session_Learnings/YYYY-MM-DD.md`. Then ask: "I captured [N] learnings from today's session. Anything else you'd like to add?" --- ## Step 8: Categorize Learnings (If Applicable) Check if any learnings should be elevated to pattern files: - **Recurring mistakes** → `06-Resources/Learnings/Mistake_Patterns.md` - **Workflow preferences** → `06-Resources/Learnings/Working_Preferences.md` Get user confirmation before adding. --- ## Step 9: Tomorrow's Setup Based on: - Incomplete items from today - Weekly priorities (especially lagging ones) - Commitments due tomorrow - Tomorrow's calendar shape Suggest 3 focus items for tomorrow: > "**Suggested focus for tomorrow (Thursday):** > > 1. **Priority 3** — It's been untouched all week and you have 2 days left > 2. **Finish pricing proposal** — 40% left, should be quick to complete > 3. **Reply to Mike** — Carried from today > > Tomorrow's shape: Moderate (4 meetings). You have a 2-hour block in the afternoon. > > Does this feel right?" --- ## Step 10: Track Usage (Silent) Update `System/usage_log.md`. --- ## Step 11: Evening Journal (If Enabled) If `journaling.evening: true`, prompt for evening reflection. --- ## Output Format Create `07-Archives/Reviews/Daily_Review_YYYY-MM-DD.md`: ```markdown --- date: YYYY-MM-DD type: daily-review plan_completion_rate: X% --- # Daily Review — [Day], [Month] [DD], [YYYY] ## 📊 Plan vs. Reality **Planned focus:** 1. [x] [Planned item 1] — ✅ Complete 2. [ ] [Planned item 2] — 🔄 In progress (X%) 3. [ ] [Planned item 3] — ❌ Didn't start **Completion rate:** X of 3 (X%) **What happened:** [Brief explanation of deviations] --- ## ✅ Accomplished - ✓ [Completed item 1] - ✓ [Completed item 2] --- ## 🔄 Progress Made | Area | Movement | |------|----------| | [Priority 1] | [What moved forward] | | [Priority 2] | [What moved forward] | --- ## 📊 Weekly Priorities Progress After today: - **Priority 1:** [Status/progress] — [emoji] - **Priority 2:** [Status/progress] — [emoji] - **Priority 3:** [Status/progress] — [emoji] **Days remaining this week:** [X] --- ## 📍 Meeting Follow-Ups ### From [Meeting Name] - [ ] [Follow-up action] — due [date] - [ ] [Follow-up action] --- ## 📺 Screen Activity (Auto-Captured) **Time by App:** | App | Time | % | |-----|------|---| | [App 1] | Xh Xm | X% | | [App 2] | Xh Xm | X% | **Metrics:** - Context switches: [X] - Longest focus: [X] minutes - Deep work ratio: [X]% **Activity Summary:** [Narrative summary from ScreenPipe] --- ## 💡 Insights - [Key realization or connection] - [Important learning] --- ## 🚫 Blocked/Stuck | Item | Blocker | Status | |------|---------|--------| | [Item] | [What's blocking] | [Status] | --- ## ❓ Discovered Questions 1. [New question that emerged] 2. [Thing to research] --- ## 📅 Tomorrow's Focus Based on weekly priorities and today's carryover: 1. [Priority 1 — tied to weekly focus] 2. [Priority 2] 3. [Priority 3] **Tomorrow's shape:** [stacked/moderate/open] --- ## 🔄 Open Loops - [ ] [Thing to remember] - [ ] [Person to follow up with] - [ ] **Awaiting:** [What you're waiting on from others] --- *Generated: [timestamp]* *Daily completion rate: X%* *Week progress: X/3 priorities on track* ``` --- ## MCP Dependencies | Integration | MCP Server | Tools Used | |-------------|------------|------------|