Travel Itinerary Skill

If key data is missing (e.g., no dates at all), produce the best possible draft with placeholders and flag gaps at the bottom.

Step 2 — Build the Markdown File

Filename: YYYY-MM-DD_[Destination].md using the departure date. Example: 2026-07-01_Spain-Morocco.md

Use this template structure, omitting any section with no data:

# [Trip Name]
**Dates:** [Departure] — [Return] ([X] days)
**Destinations:** [City 1 → City 2 → City 3]
**Budget Target:** $X,XXX total / ~$XXX/day
**Departure Point:** [Airport / City / Region]
**Purpose:** [One-line description]

---

## Logistics Overview

| Leg | Mode | Route | Date | Confirmation |
|---|---|---|---|---|
| [Origin] → [City] | Flight | [Route] | [Date] | [Code or TBD] |
| [City] → [City] | Train/Ferry/Bus | [Route] | [Date] | TBD |

---

## Anchor Events

| Event | Location | Dates | Status |
|---|---|---|---|
| [Event Name] | [City] | [Dates] | Confirmed / TBD |

---

## Day-by-Day

### Day 1 — [Date] — [City]
**Accommodation:** [Name or TBD] — [Type] — ~$XX/night
**Travel:** [Arrival details or transit]
**Activities:**
- [Activity 1]
- [Activity 2]
**Meals:** [Notable spots or budget estimate]
**Notes:** [Anything logistical — jet lag buffer, early check-in, etc.]

### Day 2 — [Date] — [City]
...

[Repeat for each day. Group consecutive days in the same city if itinerary is fluid.]

---

## Accommodation Summary

| City | Property | Type | Nights | Est. Cost | Booked? |
|---|---|---|---|---|---|
| [City] | [Name or TBD] | [Type] | X | $XXX | Yes / No |

---

## Budget Tracker

| Category | Estimated | Actual | Notes |
|---|---|---|---|
| Flights | $XXX | — | [Details] |
| Accommodation | $XXX | — | X nights avg $XX/night |
| Ground Transport | $XXX | — | Trains, buses, ferries |
| Food | $XXX | — | ~$XX/day |
| Activities & Entrance Fees | $XXX | — | [Key items] |
| Misc / Buffer | $XXX | — | Visas, SIM, incidentals |
| **TOTAL** | **$X,XXX** | **—** | |

---

## Packing List

Tailor to destination type (urban, trekking, beach, mixed). Always include the travel essentials below, then add trip-specific items.

### Always
- [ ] Passport (valid 6+ months past return)
- [ ] Travel insurance confirmation
- [ ] Downloaded offline maps (Maps.me or Google Maps)
- [ ] Local currency or notify bank
- [ ] International SIM or eSIM (check coverage for each country)
- [ ] Backup card in separate location from wallet
- [ ] Phone charger + universal adapter
- [ ] Portable battery pack
- [ ] AirTag or luggage tracker

### Clothing (carry-on optimized)
- [ ] [X] quick-dry shirts
- [ ] [X] pants/shorts
- [ ] [X] pairs socks/underwear
- [ ] Light layer / packable jacket
- [ ] Comfortable walking shoes
- [ ] [Trip-specific: hiking boots, dress shoes, etc.]

### Health & Safety
- [ ] Prescription medications (extra supply)
- [ ] OTC pain reliever, stomach meds, antihistamine
- [ ] Sunscreen
- [ ] Hand sanitizer
- [ ] [Trip-specific: altitude meds, malaria prophylaxis, etc.]

### Tech
- [ ] Camera or phone kit
- [ ] Extra batteries + charger
- [ ] SD cards
- [ ] Laptop if needed
- [ ] Headphones

### Documents (physical + digital copies)
- [ ] Passport
- [ ] Travel insurance policy + emergency number
- [ ] Accommodation confirmations
- [ ] Flight/transport confirmations
- [ ] Emergency contacts

---

## Key Contacts & Info

| Item | Detail |
|---|---|
| Travel Insurance | [Provider / Policy # / Emergency line] |
| Departure Point | [Airport / City / Region] |
| Emergency Contact | [TBD] |
| Embassy (per country) | [Link or TBD] |

---

## Open Items / To-Do

- [ ] [Book flight or transport from origin to first destination]
- [ ] [Book accommodation in X for nights Y-Z]
- [ ] [Purchase travel insurance]
- [ ] [Apply for visa if required]
- [ ] [Exchange currency or set up travel card]
- [ ] [Other flagged gaps from the data]

---

*Exported [YYYY-MM-DD] | Last updated [YYYY-MM-DD]*

Step 3 — Validate Before Exporting

Before writing the file, check for:

• Date math — day count, transit days, anchor event alignment
• Logic gaps — overnight transit without accommodation, missing arrival day
• Budget realism — flag if estimated total is significantly over or under the stated target
• Accommodation alignment — keep lodging recommendations consistent with the user's stated preference
• Routing assumptions — note when a connection or transfer is likely required

Flag issues in the Open Items section, not inline in the itinerary.

Step 4 — Create and Present the File

1. Save to /mnt/user-data/outputs/YYYY-MM-DD_[Destination].md
2. Use present_files to deliver the download link
3. Confirm: filename, date range covered, and note any flagged gaps

Rules

• No fabricated bookings. If it's not confirmed, mark it TBD.
• Budget columns stay separate. Estimated vs. Actual — never merge them. Actual fills in as the itinerary is updated.
• Packing list is trip-specific. Add or remove items based on destination, climate, and activities.
• Anchor events are fixed. Build the day-by-day around confirmed event dates — never shift them to fit travel convenience.
• Obsidian tables must render cleanly. Use pipe-formatted markdown tables throughout. All tables must be Dataview-compatible.
• No fluff. This is a logistics document. No preamble, no sign-offs, no "have a great trip!" copy.

Template Guidance

• Use placeholders when essential trip details are missing
• Preserve user supplied naming, destination order, and travel style
• Keep the output neutral and reusable so it works for solo, couple, family, or group travel