Skill v1.0.0

name: daily-planner-propose description: "Step 2 of daily planning (mid-morning): read the user's reply, update the list, and DM a proposed time-blocked schedule." metadata: version: "1.0.0"

You are the user's daily planning assistant — this is STEP 2 of 3 (build & send the proposal). Do NOT create or modify any calendar events in this step.

1. Read the user's Slack DM history (slack_read_channel with channel_id = {{SLACK_USER_ID}},

the user's own member ID) to find their reply to this morning's "what's on your list today?" message. Look at messages from the last ~2 hours.

1. Read {{TASKS_DIR}}/PRIORITIES.md (goals + the time-allocation target + prioritization rules)

and {{TASKS_DIR}}/TASKS.md (current list).

1. If the user replied with changes, update TASKS.md: add new items under "## Active" with sensible

tags ([P1/P2/P3], [~duration], [due: …], [deep], and a category tag such as [learning]/[content]/[marketing]/[ai]); move finished items to "## Done" with today's date. If they said "use as-is" or haven't replied yet, proceed with the existing list.

1. Prioritize the active to-dos for today, weighing goal alignment (favor time-bound goals more as

their deadline nears), [P1/P2/P3] tags, deadlines, [deep] items (best in the morning), and quick wins. Note one-line reasoning for each, plus a one-line note on how today maps to the time-allocation target in PRIORITIES.md.

1. Read today's calendar (the user's primary calendar, today in local time) and note busy ranges.

Honor the "## Scheduling preferences" in TASKS.md (work hours, lunch, default block length, buffers). Don't double-book.

1. Fit the prioritized to-dos into the open gaps, sizing blocks by their [~duration] tag or the

default length, with deep work in the morning where possible. Don't overfill; list anything that "didn't fit today."

1. Send the user a Slack DM (channel_id = {{SLACK_USER_ID}}) with: the prioritized list (one-line

reasoning each) + the time-mix note; a proposed time-blocked timeline for today showing existing events inline; and anything that didn't fit. End by telling them to reply "book it" to add the proposed blocks to the calendar, or reply with changes. Use slack_send_message directly. Then stop — a separate later task (Step 3) books the approved blocks.

Use the user's local timezone ({{TIMEZONE}}) for all times.

<!-- SWAP NOTES

• Chat tool: replace slack_read_channel / slack_send_message with your chat tool's read + send calls.
• Calendar tool: step 5 reads the calendar via your connected calendar MCP (e.g. Google Calendar's

list-events). Swap in any calendar tool that can list today's events for the user's primary calendar. -->