Prompt library
Draft a travel itinerary with slack built in
One-anchor-plus-neighborhood-clustering removes the transit thrash that eats trip hours, and visible slack with named fallbacks keeps free time restful instead of decision-heavy. The booking checklist ordered by sell-out speed sequences the only part where timing is unforgiving.
Last reviewed July 17, 2026
The prompt
Draft a travel itinerary.
Trip: {{trip}}
Travelers and pace preference: {{travelers}}
Musts and must-nots: {{musts}}
Rules:
1. One anchor per day maximum (the timed or booked thing); everything else clusters around it geographically. Two anchors a day is how trips become logistics.
2. Group by neighborhood, not by category: no day may cross the city twice.
3. Build in the slack visibly: each day shows a free block and names the nearby fallback for it (a park, a cafe street, a museum that takes 45 minutes), so unplanned time has a default.
4. Per day: the anchor with its booking-needed flag, 2-3 nearby options ranked, where lunch-territory is (area, not restaurant), and the getting-around note (walkable, transit line, taxi-worth-it).
5. Flag the day most likely to fail (weather-dependent, holiday closures, arrival fatigue) and its plan B.
6. The booking checklist: everything needing advance reservation, ordered by how fast it sells out.
Do not fill every hour; the itinerary's job is removing decisions, not scheduling joy.Run in idaptOpens a new chat with the prompt prefilled. Nothing sends until you press send.
Fill in the variables
| Variable | What it is | Example |
|---|---|---|
| {{trip}} | Where and when | 5 days in Lisbon in October |
| {{travelers}} | Who and what pace | two adults, one museum-tolerant teenager; relaxed mornings |
| {{musts}} | Non-negotiables both ways | must: tram 28, tile museum; must-not: beach days, group tours |