Alfred

Todoist Quick Reference

⚔️ Main Quests (6g6f74cmqrRj2937)

• 💰 Income (6g6f74h58rpwpv47) — Upwork, portfolio, templates, content, freelance
• 🧠 Growth (6g6f74jhHXCVgxW7) — English, Docker, technical skills, learning
• 👨‍👩‍👧 Family (6g6f74jrXXg5Pp37) — baby prep, family events, Duyên support
• 🏆 Milestones (6g6h7Qfmj6MGFV97) — phase decision points ONLY

🎮 Side Quests (6g6f74h9JQXGVX6p)

• 🎯 Passion (6g6f74jRJwPPCmWp) — Wildtide, Bookie, creative projects
• 🏠 Life (6g6f74qmvFxphmJG) — admin, errands, purchases, household

Read references/todoist-structure.md — full labels (energy + topic), priority convention, daily habits reference. Read when creating/updating tasks.

Step 0: Pre-flight Brain Check (Mode 2 + Mode 5 only)

Skip for Mode 1 (add event), Mode 3 (cleanup), Mode 4 (add quest) — context is already dense enough.

For Mode 2 (Optimize) and Mode 5 (Weekly Review):

• brain_recall(query="schedule patterns [day-type] [user-modifications]", type="pattern", project="digital-identity", time_range="-90 days", k=5)
• Day-type: "weekday"/"weekend"/"early-wake"/"late-wake" — infer from wake time detection in Step 3
• If results found: note patterns as soft constraints (not overrides) during proposal building
• If empty: proceed normally — brain will accumulate patterns over time
• NEVER let recalled patterns override science-engine rules — science is the floor, patterns are refinements

Step 1: Parse Input

Extract from $ARGUMENTS and user message:

• Date: explicit date, "today"/"hôm nay", "tomorrow"/"ngày mai". No date → today (or tomorrow if after 20:00).
• Event/task details: what, where, when, duration
• Mode: detect from keywords:
  • Mode 1 (default for event-like input): has time, location, or date-specific constraint
  • Mode 2: optimize, replan, sắp xếp, tối ưu
  • Mode 3: cleanup, reschedule, dọn, skip, audit, health check, kiểm tra
  • Mode 4: quest, task, thêm task, add, tạo — or task-like content without time/location

Routing:

• Mode 3 (cleanup) → skip to "Mode 3: Cleanup" section
• Mode 4 (add quest) → skip to "Mode 4: Add Quest Flow" section
• Mode 5 (weekly review) → skip to "Mode 5: Weekly Review" section
• Mode 1 & 2 → continue to Step 2

Google Calendar Reference

All datetimes use RFC3339 without offset: YYYY-MM-DDTHH:MM:SS with timeZone: "Asia/Ho_Chi_Minh". Read from primary calendar (ignore Todoist sync duplicates). Create/update with calendarId: "primary", sendUpdates: "none", reminders: {"useDefault": false}. For updates/deletes, use calendarId + id from gcal_list_events response.

Step 2: Gather Data (parallel)

Call these in parallel:

1. gcal_list_events — target date (timeMin YYYY-MM-DDT00:00:00, timeMax YYYY-MM-DDT23:59:59, timeZone Asia/Ho_Chi_Minh). Also fetch day before and day after if travel/early wake involved.
2. mcp__todoist__find-tasks-by-date — startDate = target date. If Todoist MCP is unavailable, proceed with gcal-only data and note "Todoist unavailable — task suggestions skipped" in the proposal.
3. Bash: run date +"%H:%M" — current time in system timezone. Store as NOW.

Step 3: Determine Wake Time & Baseline Skeleton

Current Time Awareness

Use NOW (from Step 2) to split the day:

• PAST: events/tasks whose end time < NOW → already happened, do not reschedule
• IN PROGRESS: events where start < NOW < end → currently active
• FUTURE: events/tasks whose start time >= NOW → available for scheduling

Scheduling constraint: All new task/event placement MUST start from NOW, not from wake time. Past slots are locked.

Mode 2 (optimize): Only rearrange FUTURE slots. PAST events stay as-is. IN PROGRESS events keep their original end time.

Mode 1 (add event + replan): Cascade only affects FUTURE events. PAST events are informational only.

Default daily skeleton (wake 06:00 — applies ANY day, Duyên's schedule is variable including weekends):