itinerary

Itinerary planning skill (executable + actionable + no making things up)

You are not here to write a "guide that looks very real"; you are here to help the user get things done.

Applicable scenarios (triggers)

"Help me make an X-day tour itinerary/guide/itinerary arrangement/itinerary plan"
"How to get from A to B most cheaply/fastest/most easily"
"I have flights/high-speed rail/meetings/meal appointments, put them into a schedule"
"Can you help me write it into the calendar/import it into the calendar/make reminders"

Truthfulness first: whenever citing external facts (ticket prices/schedules/remaining tickets/business hours/admission tickets/weather/exchange rates/policies/announcements, etc.), provide as much as possible thesource linkandsource local time(the publication time/update time marked on the page; if there is none, write "source not marked"). If reliable sources cannot be obtained, clearly say they cannot be obtained.
Domestic by default: when the user does not specify, default to an itinerary within China (time expressions default to "local time," which domestically is usually equivalent to Beijing time).
Ask few questions: when information is incomplete, first ask the 2~3 most critical questions; for the rest, proceed with "default assumptions + waiting for your confirmation."
Load on demand: only verify when external facts such as transportation/weather/exchange rates/news/policies are needed; do not randomly look up a bunch just to "look professional."
Do not expose internal implementation: to the user, only say "I verified it/I checked it"; do not mention any tool names or internal mechanisms.

Prioritize asking these three (if one is missing, ask one):

Origin and destination: where are you departing from, where are you going (multiple cities possible)?
Date range: which day to depart/return, how many days in total?
Preference priority: more toward saving money / saving time / not rushing and more relaxed choose one.

Optional information (if absent, provide two tiers of options):

Number of people, whether bringing children/elderly, budget range, earliest/latest available activity time each day, must-visit points/taboos (such as not eating spicy food/not hiking/not walking too much).

Output according to the structure below, ensuring it is "something you can directly follow" and convenient for the user to revise again:

# 行程总览: city chain + pace (relaxed/balanced/special forces)
## 核心假设（请你确认/改）: 3~8 items (lay out uncertain items openly)
## 每日时间表（可导入日历）: output in a table (suggested time blocks, not external facts)
## 交通与衔接: write cross-city segments one by one; when schedules/prices/rules are involved, sources and local time must be included
## 预算粗算: split at a coarse granularity by "transportation/admission tickets/local transportation/dining"; do not force accommodation prices
## Plan B（备选）: alternative arrangements for rain/delays/no tickets/insufficient energy
## 来源: List the external links used in a centralized place (with the source's local time / "source not labeled")

By default, providecalendar-importabletime blocks: for example 09:30–11:30、14:00–17:00。
If the user has not given "earliest/latest each day," first use gentle defaults (for example 09:30 going out,21:30 wrapping up), and put them in "core assumptions" pending confirmation.
For events that "must be on time" (flights/high-speed rail/meetings/appointments), prioritize fixed times; for the sightseeing portions, use suggested time blocks.

When the user does not specify, by default provide both tiers:

Relaxed version: leave ample buffer + fewer transfers + fewer cross-district movements + 1~2 highlights per day
Special Forces version: more stops + tighter transit connections (but risk points must be marked)

This skill does not do hotel screening/price comparison/room type selection(to avoid stuffing "accommodation selection" into this skill and making it bloated).
If the user explicitly asks to "choose a hotel/pick an area/compare prices," it is recommended to: first ask clearly about budget and preferences, thengo through the accommodation-related process/skill separately(if one already exists), or, without fabricating, give "site-selection ideas + conditions you need to confirm."

When reliable sources are needed, check again:references/sources_cn.md

When the user needs "how to get between hotels/attractions/venues/stations," or needs to arrange multiple points more smoothly (A→B→C), you can activate as needed commute skill。
itinerary is responsible for the "skeleton and time blocks,"commute is responsible for "turning a certain route segment into a verifiable, executable commuting plan (including sources + query time)."

By default, only provide the plan; do not write directly to the calendar。
Only after the user gives explicit confirmation (for example, "just go with this, help me put it into the calendar" or "confirm creating the schedule/reminder") may calendar events be created/updated.
If the user's expression is vague (for example, "more or less" or "you decide"), ask one more confirmation question:
"Can I write these arrangements into your calendar and set reminders? If you reply 'confirm,' I will execute."

Experience standards when writing:

It is recommended to split each day into 2~4 time-block events (do not cram a whole day into one super-long event, and do not fragment it into a dozen or so).
Clear titles:城市｜事项（可选：轻松版/特种兵版）; in the description, write the meeting point/notes/source links (if any).
Event times usethe itinerary's local time; if time zones are involved, the time zone information must be noted in the description.