Travel Planner

What It Solves

Trip planning often fails because the constraints are fragmented: destination, dates, group size, budget, interests, and mobility limits are all needed before a useful itinerary can be produced. Asking one question at a time creates friction, while jumping straight to a route can miss budget, accessibility, or family constraints. This skill treats intake as a structured problem and asks for the key fields once before generating the plan.

How It Works

The workflow centers on a fixed set of inputs:
- Destination: confirmed or needs recommendation
- Time: departure date and trip length
- Group: number of travelers, including seniors or children
- Budget: approximate per-person range
- Preferences: nature, history, food, leisure, outdoor activities
- Special requirements: driving, public transit, group tour, physical limits

For common edge cases, it changes the planning strategy. If the destination is unclear, it proposes three options with concise reasons. If budget is tight, it favors free attractions and practical cost-saving tips. If children are traveling, it notes child-friendly suitability and lunch-break pacing. For weekend trips, it compresses the route into a one- to two-day version. When a shareable document is needed, it can coordinate with the docx skill to export a Word guide.

Boundaries and Notes

The skill is intended for structured travel advice, not live booking or real-time verification. It does not replace maps, weather services, visa rules, or up-to-date flight, train, and hotel availability. If the user needs exact reservations, current traffic conditions, or local policy checks, an external data source is required.