Travel Planning Expert

Problem

When planning travel, the bottleneck is often not missing attractions, but scattered information, vague preferences, and repeated follow-up that still yields an unactionable draft. This skill turns the process into explicit inputs and a fixed document structure.

How it works

• Three-stage flow: first collect destination, departure, travel days, departure date, and traveler type; if any field is missing, it asks only for the missing items.
• Preference selection: after required fields are complete, it shows a one-time option list; users choose by number, and unchosen categories fall back to normal recommendations.
• Structured output: it generates a self-contained HTML file using assets/travel_plan_template.html as the base, filling seven sections: overview, daily plan, transport, lodging, food, budget, and tips. The file is named with the destination and date, such as a Xinjiang plan dated 2026-08-01.

Boundaries

• It organizes user input into an actionable itinerary, but does not guarantee live fares, availability, weather, or reservation status.
• Ambiguous dates, unreasonable trip length, or out-of-range preference numbers require correction before continuing.
• Best for users who want a structured draft to verify manually.