pace-morning

name	pace-morning
description	Review tomorrow's wake on the user's Pace iPhone alarm and propose changes (move, skip, note, or a new one-off wake) using the pace MCP tools. Use when the user asks when they are waking up, wants to change tomorrow's alarm, mentions an early flight/meeting/holiday, or asks for a morning plan.
argument-hint	[what changed, e.g. 'flight at 9:40' or 'holiday tomorrow']
allowed-tools	mcp__pace__get_next_wake mcp__pace__list_upcoming_wakes mcp__pace__propose_wake mcp__pace__move_occurrence mcp__pace__skip_occurrence mcp__pace__set_occurrence_note

Pace morning review

Pace is the user's iPhone alarm. The pace MCP tools read their upcoming wakes and queue changes as intent. The iPhone applies queued intents on its next sync and is the only thing that rings. You cannot fire or silence an alarm.

Procedure

1. Read before writing. Call get_next_wake, and list_upcoming_wakes (days: 2 for "tomorrow", 7 for a week). Note tz; every time you say or send is in that zone. Note pending_intent_ids: those occurrences already have unapplied changes — do not queue a duplicate.
2. Decide what should change, from the user's message and anything else in context (calendar, travel, a stated reason). Rules of thumb:
   • Need to be somewhere at T → wake at T − (commute + 45 min prep), rounded to 5 min. Say the arithmetic.
   • Holiday / day off → skip_occurrence, never delete the alarm.
   • A day with no wake that needs one → propose_wake with a one-line reason naming the event.
   • The alarm is fine but the morning has a reason → set_occurrence_note.
3. Confirm before writing when the change is large (more than 30 min earlier, or a skip), unless the user already told you the outcome they want.
4. Write once. Use the occurrence_id from step 1. The tool returns deduplicated: true if it was already queued — treat that as success.
5. Report in one or two lines: old time → new time (with tz), the reason you set, and "Pace will apply this when the app next syncs." If warning said the phone has not synced yet, say so.

Do not

• Do not call write tools speculatively or in a loop; one intent per change.
• Do not invent occurrence ids; they are <alarm_id>@<YYYY-MM-DD> and come from list_upcoming_wakes.
• Do not promise the alarm changed; it changes when the phone applies it.

$ARGUMENTS