Plan your day across ServiceNow incidents and TickTick tasks

**Objective:** Produce one ordered plan for {person-name} for the next {days-ahead} days (default 1), combining TickTick tasks with the ServiceNow work assigned to that person.

**Step 1: TickTick work (TickTick MCP)**

Call `ticktick-get-tasks` with `due-date.to` set to the end of the window, keeping only tasks that are not completed. Include overdue tasks. Note title, project, priority (0 None, 1 Low, 3 Medium, 5 High) and due date.

**Step 2: ServiceNow work (ServiceNow MCP)**

Call `servicenow-get-incident` with `assigned-to` set to `{person-name}`; keep incidents whose state is not Resolved or Closed. Then call `servicenow-get-task-sla` with `task` set to each incident number (or one call with `active` true and `breach-time.to` set to the end of the window, matched back to those incidents). Note `breach-time`, `actual-elapsed-percentage` and `has-breached`.

**Step 3: Merge**

Order the combined list: breached or breaching SLAs first, then priority 1 - Critical and 2 - High incidents, then overdue TickTick tasks, then the rest by due date. If a TickTick task title cites an incident number already in the list, show them as one line.

**Step 4: Report**

A numbered plan: item, source (TickTick or ServiceNow), due or breach time, why it is placed there. End with a short list of items that could not be fitted in the window.

**Rules & Guidelines:**

* `ticktick-get-tasks` is on the TickTick MCP server. `servicenow-get-incident` and `servicenow-get-task-sla` are on the ServiceNow MCP server.
* Read-only. Do not call `ticktick-add-task`, `ticktick-update-task`, `ticktick-complete-task`, `servicenow-update-incident` or `servicenow-add-incident`.

**Validation:**

* If either server returns nothing, plan from the other and say which side was empty.
* If `{person-name}` matches no ServiceNow user name exactly, report that the ServiceNow side was skipped rather than guessing a name.