AgentSkillsCN

obs-plan-my-day

交互式每日计划——整合 Todoist 任务、Obsidian 项目以及近期笔记,通过对话帮助你优先安排一天的日程。

SKILL.md
--- frontmatter
name: obs-plan-my-day
description: "Interactive daily planning - integrates Todoist tasks, Obsidian projects, and recent notes to help prioritize your day through conversation."

Plan My Day Skill

Workflow Position

code
[Start of day]
        |
    personal:obs-plan-my-day     <- YOU ARE HERE
        |
    [Gather All Context]
        |
    ┌───────────────────────────────────────┐
    │  Todoist Tasks (due today + overdue)  │
    │  Active Projects (1-Projects/)        │
    │  Recent Notes (last 3 days)           │
    │  Upcoming Deadlines                   │
    └───────────────────────────────────────┘
        |
    [Deep Analysis] -> What matters most? -> What's blocked?
        |
    [Interactive Prioritization Conversation]
        |
    [Generate Prioritized Plan]
        |
    Output: Clear focus + Action plan + Updated daily note

Overview

Interactive daily planning skill that synthesizes information from multiple sources to help you focus on what matters. Uses deep thinking to analyze your commitments and guides you through prioritization via conversation.

Key Features:

  • Pulls tasks from Todoist (today, overdue, upcoming)
  • Scans active Obsidian projects for context
  • Reviews recent notes for continuity
  • Analyzes workload and identifies conflicts
  • Conversational prioritization process
  • Outputs clear, actionable daily focus

Primary Value: Start each day with clarity about what truly matters.


When to Use

  • Start of each work day
  • After a break or vacation (catch-up mode)
  • When feeling overwhelmed by tasks
  • Sunday evening (week planning mode)
  • Before important deadlines

When to Skip

  • Clear day ahead - You already know your focus
  • Crisis mode - Just handle the emergency first
  • Deep work day - Already committed to one task

The Process

Step 1: Gather Context from All Sources

Todoist Tasks: Using Todoist MCP tools, fetch:

  • Tasks due today
  • Overdue tasks
  • Tasks due this week (upcoming)
  • Tasks by project

Present Todoist summary:

markdown
## Todoist Overview

**Today:** 8 tasks
**Overdue:** 3 tasks ⚠️
**This Week:** 15 tasks

### By Priority
| Priority | Count | Examples |
|----------|-------|----------|
| P1 (Urgent) | 2 | "Submit quarterly report", "Fix prod bug" |
| P2 (High) | 4 | "Review PR #123", "Prepare slides" |
| P3 (Medium) | 5 | ... |
| P4 (Low) | 2 | ... |

### Overdue ⚠️
1. [ ] "Follow up with Sarah" (2 days overdue)
2. [ ] "Update project timeline" (1 day overdue)
3. [ ] "Send meeting notes" (1 day overdue)

Obsidian Projects: Scan 1-Projects/ for active projects:

  • Projects with status: active
  • Recent modifications
  • Upcoming due dates from frontmatter
  • Related meeting notes

Present project context:

markdown
## Active Projects

### [[LeanIX]] `#p/leanix`
- **Status:** Active
- **Due:** 2024-02-15 (12 days)
- **Recent:** [[2024-01-14 - LeanIX Architecture Review]]
- **Notes this week:** 3

### [[BCBS239]] `#p/bcbs239`
- **Status:** Active
- **Due:** 2024-03-01 (26 days)
- **Recent:** [[BCBS239 Data Mapping]]
- **Notes this week:** 1

Recent Activity:

  • Last 3 daily notes (for continuity)
  • Yesterday's blockers and carry-forwards
  • Recent meeting action items
markdown
## Recent Context

**Yesterday's Blockers:**
- API integration waiting on credentials from IT

**Carried Forward:**
- Finalize presentation deck

**Recent Meetings:**
- [[2024-01-14 - LeanIX Standup]] - Action: Update architecture diagram
- [[2024-01-12 - BCBS239 Review]] - Action: Schedule follow-up with compliance

Step 2: Deep Analysis

Think deeply about the gathered context:

Workload Analysis:

  • Total commitments vs available time
  • Conflicting priorities
  • Dependencies and blockers
  • Energy-appropriate task matching

Priority Signals:

  • Deadlines approaching
  • Overdue items (catch-up needed?)
  • Stakeholder expectations
  • Personal energy and focus capacity

Risk Assessment:

  • What happens if X doesn't get done today?
  • What's blocking the most important work?
  • Are there quick wins that unblock others?

Present analysis:

markdown
## Analysis

### Workload Assessment
**Estimated hours of work:** 12 hours
**Available focused time:** 6 hours
**Gap:** 6 hours - **prioritization required**

### Key Observations

1. **Deadline Pressure:** LeanIX due in 12 days, but architecture review feedback not incorporated yet
2. **Overdue Pattern:** 3 tasks overdue - mostly communication/follow-up tasks
3. **Blocker:** API credentials still pending - this blocks 2 P1 tasks
4. **Quick Wins:** Meeting notes and PR review could clear mental load

### Recommended Focus

**If you could only do ONE thing today:**
> Complete the LeanIX architecture diagram update - it unblocks the team and addresses deadline risk

**Top 3 for realistic day:**
1. LeanIX architecture diagram (2h) - Deadline risk
2. Fix prod bug (1h) - P1, customer impact
3. Clear overdue follow-ups (30min) - Reduce mental load

Step 3: Interactive Prioritization

Engage in conversation to refine priorities:

Based on my analysis, here's what I recommend for today:

  1. 🎯 LeanIX architecture diagram (2h) - Deadline risk, team blocker
  2. 🔥 Fix prod bug (1h) - P1, customer impact
  3. 📧 Clear 3 overdue follow-ups (30min) - Mental load reduction

Questions to consider:

  • Does the prod bug need to come first? Is it actively affecting users?
  • Are there any meetings today that change the available time?
  • Is there energy/focus available for deep work (architecture) or is it a "admin day"?

What feels right to you?

Wait for user input. Adjust based on:

  • User's energy level
  • Meetings not captured in notes
  • External pressures not visible in data
  • Personal preferences

Step 4: Generate Plan

After conversation, create actionable plan:

Time-Blocked Schedule (if requested):

markdown
## Today's Plan: 2024-01-15

### Morning (High Energy)
- [ ] 09:00-11:00 - LeanIX architecture diagram
- [ ] 11:00-11:30 - Clear overdue follow-ups

### Midday
- [ ] 11:30-12:00 - Buffer / emails
- [ ] 12:00-13:00 - Lunch

### Afternoon
- [ ] 13:00-14:00 - Fix prod bug
- [ ] 14:00-15:00 - LeanIX standup meeting
- [ ] 15:00-17:00 - Continue architecture work

### End of Day
- [ ] 17:00-17:30 - Daily note wrap-up

Priority List (simpler):

markdown
## Today's Priorities

### Must Do (Non-negotiable)
1. [ ] LeanIX architecture diagram update `#p/leanix`
2. [ ] Fix prod bug (JIRA-1234) `#p/bcbs239`

### Should Do (If Time Permits)
3. [ ] Clear 3 overdue follow-ups
4. [ ] Review PR #123

### Won't Do Today (Consciously Deferred)
- Prepare Q2 slides (moved to tomorrow)
- Research new framework (moved to Friday)

Step 5: Update Daily Note

Offer to create/update today's daily note with the plan:

Would you like me to:

  1. Create daily note with this plan (runs obs-daily-notes)
  2. Update existing note with priorities
  3. Just keep the plan in this conversation

Integration Points

Todoist MCP Tools Used

ToolPurpose
find-tasks-by-dateGet today's and overdue tasks
find-tasksGet tasks by project
get-overviewGet project structure
user-infoGet timezone and preferences

Obsidian Integration

SourceData Extracted
1-Projects/Active projects, due dates
5-Daily/Recent daily notes, blockers
Meeting notesAction items, context
FrontmatterStatus, priority, dates

Modes

Standard Mode

Full analysis with all sources. Use for normal work days.

Quick Mode

Just Todoist tasks + top projects. For when you need fast clarity.

"Quick plan: Your top 3 for today based on Todoist priorities..."

Catch-Up Mode

Extended analysis after time away. Reviews full week of notes and all overdue items.

Week Planning Mode

Sunday/Monday overview of the week ahead. Includes:

  • All tasks due this week
  • Project milestones
  • Meeting load analysis
  • Energy distribution suggestions

Output

Conversation Summary

At end of planning session:

markdown
> "Planning complete! Here's your day:"
>
> **Focus:** LeanIX architecture diagram
>
> **Must Do:**
> 1. LeanIX architecture diagram (2h)
> 2. Fix prod bug (1h)
>
> **Deferred to Tomorrow:**
> - Q2 slides preparation
>
> **Blockers Identified:**
> - API credentials (follow up with IT)
>
> **Daily note:** Updated with priorities

Optional: Todoist Updates

If desired, can update Todoist:

  • Reschedule deferred tasks
  • Add new tasks identified in planning
  • Update priorities

After Planning

  1. Start the focus task - No more planning, do the work
  2. Update daily note - As you complete tasks
  3. End of day review - What got done? What carries forward?
  4. Run tomorrow - Build the habit

Key Principles

  • Integration over silos - Combine Todoist + Obsidian for full picture
  • Deep thinking - Don't just list tasks, analyze what matters
  • Conversation refines - Your input improves the AI's recommendations
  • One focus - Every day should have ONE clear priority
  • Realistic planning - Account for meetings, energy, interruptions
  • Conscious deferral - Choosing not to do something is a valid decision
  • Action, not planning - The goal is clarity to enable action