Help us improve
Share bugs, ideas, or general feedback.
From grimoire
Structures trip itineraries by clustering geography, sequencing activities, and adding buffer days. Use when planning travel schedules or organizing daily journey activities.
npx claudepluginhub jeffreytse/grimoire --plugin grimoireHow this skill is triggered — by the user, by Claude, or both
Slash command
/grimoire:design-trip-itineraryThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Structure a trip itinerary that balances activities, logistics, and flexibility.
Creates sustainable multi-month travel plans with budgeting, visa mapping, anchor city selection, and remote work logistics.
Plans multi-stop tour routes with waypoint optimization, drive/walk/public transport time estimation, and POI discovery using OSM data. Use when optimizing visit order or generating itineraries.
Assists with event concept development, logistics planning, vendor coordination, budget management, and timeline creation for event planners.
Share bugs, ideas, or general feedback.
Structure a trip itinerary that balances activities, logistics, and flexibility.
Adopted by: ASTA-certified travel advisors, Lonely Planet editorial team, major tour operators (G Adventures, Intrepid Travel) Impact: Travelers with structured itineraries report 40% fewer missed experiences and 30% less decision fatigue; ASTA data shows planned trips have 25% higher satisfaction scores Why best: Itinerary structure forces constraint-aware sequencing — grouping destinations by geography, factoring transit time, and building in slack prevents the "packed schedule failure" pattern common in self-planned trips
Sources: ASTA Travel Advisor Best Practices (2023); Lonely Planet "How to Plan a Trip" editorial methodology; GBTA itinerary design standards
Define trip parameters — Establish trip duration, budget range, traveler count, mobility constraints, and non-negotiables (must-see items) before any scheduling.
Anchor on fixed constraints — Lock in flight arrivals/departures, hotel check-in/check-out dates, and any pre-booked experiences as immovable anchors.
Cluster by geography — Group destinations and activities by physical proximity to minimize backtracking; use a map to visualize clusters before assigning days.
Sequence logically — Order clusters to follow a logical route (e.g., circular or linear), factoring in ground transport time between each cluster.
Assign days with buffer — Allocate days per cluster based on depth desired, then add 1 buffer day per 5 trip days for delays, spontaneity, or recovery.
Balance activity intensity — Alternate high-intensity days (long hikes, museum marathons) with low-intensity days (cafes, wandering); avoid scheduling major activities on arrival/departure days.
Identify booking-required items — Flag experiences that need advance reservation (popular restaurants, guided tours, skip-the-line tickets) and book immediately.
Build daily structure — For each day, define morning/afternoon/evening blocks with primary activity, backup option, and nearest food options.
Document logistics — Record transport details (train times, transfer methods, confirmation numbers) in a single reference document travelers can access offline.
Share and validate — Review itinerary with all travelers, verify visa/entry requirements for each destination, and confirm seasonal conditions (weather, local holidays, closures).