/daily-plan

name: daily-plan
description: "Build today's plan from calendar, tasks, priorities and commitments, with smart scheduling suggestions. Use when the user says 'plan my day', 'what's on today', 'help me focus', or starts the morning. Also use proactively at the first session of the day. Not for reviewing a finished day; use `daily-review`."
model_routing:
  default: balanced
  steps:
    data-gathering: fast
    synthesis: balanced
hooks:
  Stop:
    - type: command
      command: "node .claude/hooks/daily-plan-quick-ref.cjs"

Execution mode

Run inline in the current conversation by default, so this work can see what the user has already discussed, decided, or settled this session. Do not fork merely because this skill was selected. Only run in the background when the user explicitly asks for a background run or the host has already obtained a specific background-work approval for this run.

Delegated gathering (large-vault scaling)

This skill stays inline as described above: it keeps session awareness, it asks the user the questions, and it owns every interactive step. What it does NOT do inline is the bulk read-gathering, which on a mature vault (hundreds of notes, thousands of indexed messages, a live calendar and multiple integrations) can be large enough to exhaust the main conversation before the useful work starts.

So the gathering phase is delegated to one `general-purpose` subagent via the Agent tool, using the self-contained prompt in this skill's `AGENT_INSTRUCTIONS.md`:

1. Read `.claude/skills/daily-plan/AGENT_INSTRUCTIONS.md`. 2. Substitute its placeholders (`{{TARGET_DATE}}`, `{{TARGET_DATE_PLUS_1}}`, `{{DAY_NAME}}`, `{{MONTH}}`, `{{DD}}`). 3. Call the Agent tool with `subagent_type: "general-purpose"`, `model: "sonnet"`, that prompt, and a short description. The brief is mechanical gathering, so it runs on the fast tier declared by this skill's `model_routing.steps.data-gathering`; the judgement calls stay in this conversation on the default model. 4. Verify it wrote the draft plan to the resolved daily-plan folder (see Daily plan folder), then run the remaining interactive steps from its findings and present the plan. 5. **Close out every `<!-- NEEDS TASK -->` line in the draft.** The subagent never creates tasks, so a focus candidate with no existing task is written without a checkbox and marked. For each one: confirm it with the user per Step 6, create the task with `create_task`, then rewrite that line as a `- [ ]` checkbox carrying the returned `^task-YYYYMMDD-XXX` anchor and remove the marker. If the user declines, remove the marker and leave the line checkbox-free. Never leave the marker in the saved plan, and never turn one of these lines into a checkbox without an anchor — an anchorless checkbox is invisible to completion sync forever (Step 6).

The subagent inherits MCP connections, runs in its own context, and that context is freed when it completes, so only its findings reach this conversation.

**Use `AGENT_INSTRUCTIONS.md` verbatim.** Read the file and pass its content as the subagent prompt, substituting only the placeholders. Do NOT hand-write a replacement brief from what you already know about the day: that is how steps get silently dropped, and the omission looks complete because nothing errors. If context from this conversation is worth adding, APPEND it to the file's content; never substitute for it.

**Two caveats that are load-bearing:**

• **Do not count on hooks for the subagent's writes.** The hooks declared in

this skill's own frontmatter belong to this skill's run, not the subagent's, and whether the repository-wide hooks in `.claude/settings.json` reach a subagent's tool calls is not something a skill should assume either way. Nothing in this skill's gathering depends on a hook; the subagent's writes must stand on their own.

• **Always fall back.** If the subagent fails, times out, or returns nothing

usable, say so plainly and run the gathering inline from the same `AGENT_INSTRUCTIONS.md`. A missing subagent must never mean a missing result.

**Stays inline:** the journal and Monday week-planning gates, the yesterday's review check, Dex Inbox triage, the meeting-task review and goal-link confirmations, inbound external task review, pushing focus tasks to Reminders, and usage tracking. These need the user, so they must not be delegated.

Previous-working-day notes (Step 5.10c) are gathering, not the yesterday's review check. That step lives in `AGENT_INSTRUCTIONS.md` so a customization of it reaches the subagent. The written plan must show the post-condition: notes found for a named date/file, or none.

Purpose

Generate your daily plan with full context awareness. Automatically gathers information from your calendar, tasks, meetings, relationships, and weekly progress to create a focused plan with genuine situational awareness.

Usage

• `/daily-plan` — Create today's daily plan
• `/daily-plan tomorrow` — Plan for tomorrow (evening planning)
• `/daily-plan --setup` — Re-run integration setup

---

Tone Calibration

Before executing this command, read `System/user-profile.yaml` → `communication` section and adapt tone accordingly (see CLAUDE.md → "Communication Adaptation").

---

Step 0: Process Unprocessed Meetings (only when something is waiting)

Before gathering context, ask the session-start sweep how many meeting records are still waiting, without re-scanning the vault yourself. The count mode prints one integer, bypasses the sweep's once-per-30-minutes notice throttle, and writes nothing, so it is safe to call every morning:

node .claude/hooks/meeting-queue-check.cjs --count

Branch on the answer:

• **`0`:** skip this step entirely and say nothing. Yesterday evening's review

already ran the catch-up pass, so on most mornings this is the answer, and re-running a full seven-day `/process-meetings` here found nothing new while costing mi