Daily Plan

Generate structured daily plans with time-blocked schedules based on active tasks, calendar events, and email follow-ups. Outputs follow template.md.

---

Language

See METHODOLOGY.md language mirror rule. Reply in the user's language.

---

Data Sources

Gather information from these sources (skip any unavailable):

1. Active tasks — Read from ~/Tandem/tasks/kanban.md. Parse tasks in "📝 To Do" and "🚀 In Progress" columns. Focus on tasks due today, overdue, and high-priority.
2. Calendar events — If connected, pull today's meetings and appointments to avoid scheduling conflicts.
3. Email follow-ups — Read from ~/Tandem/email/MEMORY.md for follow-ups due today.
4. User preferences — Check Personal Preferences for work schedule (start time, end time, preferred deep work hours).

---

Workflow

Step 1: Gather Context

Read all data sources silently. Identify:

• Fixed commitments (calendar events)
• Tasks to schedule (from task-manager, overdue first)
• Follow-ups due
• Available time blocks

If no tasks exist:

You don't have any tracked tasks yet. Want to add some first?

AskUserQuestion:
  - "Yes — let me add tasks"
  - "Just give me a blank daily template"
  - "Skip — I'll manage manually today"

Step 2: Draft Plan

Create a time-blocked schedule using these default blocks (adjust based on user's stated work schedule):

Block	Default Time	Purpose
Morning Focus	08:00 - 11:00	Deep work — hardest/most important tasks
Midday	11:00 - 13:00	Meetings, calls, collaborative work
Lunch	13:00 - 14:00	Break
Afternoon	14:00 - 16:00	Email, admin, follow-ups, lighter tasks
Wrap-up	16:00 - 17:00	Review, plan tomorrow, tie up loose ends

Assignment rules:

1. Calendar events are fixed — schedule around them
2. Urgent/overdue tasks get the first available deep work slot
3. High-priority tasks fill remaining morning focus time
4. Email follow-ups go in the afternoon block
5. Medium/low tasks fill remaining afternoon slots
6. If too many tasks for the day, flag overflow and suggest prioritization

Step 3: Present Plan

Show the proposed plan and ask for approval:

Here's your plan for today:

[Formatted plan per template.md]

AskUserQuestion:
  - "Looks good — save it"
  - "Adjust — move some things around"
  - "Add more tasks to the plan"
  - "Start from scratch"

Step 4: Adjust (if requested)

If user wants to adjust:

What would you like to change?

AskUserQuestion:
  - "Move [task] to a different time block"
  - "Remove a task from today"
  - "Add a task I forgot"
  - "Change the time blocks"

Handle the adjustment and re-present the plan.

Step 5: Save

Save the approved plan to ~/Tandem/tasks/daily-plan-[YYYY-MM-DD].md.

Confirm:

Plan saved! Your top priority for this morning: **[top task]**

---

Overflow Handling

When there are more tasks than available time:

You have more tasks than time today. I've fit in [X] of [Y] tasks.
These didn't make the cut:

- **[Medium]** [Task] — Due: [date]
- **[Low]** [Task] — Due: [date]

AskUserQuestion:
  - "That's fine — carry them to tomorrow"
  - "Let me reprioritize"
  - "Cancel some of these tasks"

---

Proactivity Hooks

After saving the plan:

AskUserQuestion:
  - "Sync this plan with my Monday.com board"
  - "Start working on the first task"
  - "Nothing else — I'm ready to go"

At end of day (if the user returns):

How did today go? Want to do a quick review?

AskUserQuestion:
  - "Quick check — mark tasks as done"
  - "Full review — what went well, what didn't"
  - "Skip — I'll handle it"

---

Task Format

When creating tasks in kanban.md, follow the canonical format in tandem-skills/tasks/task-manager/references/kanban-format.md.

Key rules:

1. Read <!-- Config: Last Task ID: NNN --> from kanban.md to get the next ID
2. Increment the counter: if last ID was 005, next task is TASK-006
3. Write the updated counter back: <!-- Config: Last Task ID: 006 -->
4. Use canonical format: ### TASK-XXX | Title (H3, 3-digit zero-padded, pipe separator)
5. Meta on ONE line: **Priority**: X | **Category**: X | **Assigned**: @user

---

Anti-Patterns

• Do NOT create a plan without reading existing tasks first
• Do NOT schedule over fixed calendar events
• Do NOT overload the day — respect realistic time estimates
• Do NOT forget lunch/breaks — always include downtime
• Do NOT save the plan without user approval
• Do NOT ask open-ended questions when AskUserQuestion can be used

Activity Logging

After completing the workflow, append an entry to ~/Tandem/stats.json:

{
  "type": "system",
  "action": "daily-plan",
  "count": 1,
  "timeSavedMinutes": 15,
  "description": "Daily plan created: 6 time blocks, 3 priorities",
  "timestamp": "<current ISO 8601>"
}

If ~/Tandem/stats.json does not exist, create it as [<entry>]. If it exists, read it, parse the JSON array, append the new entry, and write it back.

Dashboard Sync

After appending to stats.json, follow the /sync workflow from tandem-skills/core/sync/SKILL.md to rebuild ~/Tandem/dashboard.html with updated statistics. This keeps the dashboard current after every skill run. If /sync fails (e.g., dashboard.html does not exist yet), continue — the main skill workflow must complete successfully regardless of sync outcome.