You MUST use a todo list to complete these steps in order. Never move on to one step if you haven't completed the previous step. If you have multiple read steps in a row, read them all at once (in parallel).

Add all steps to your todo list now and begin executing.

## Steps

1. Check `./documents/trips/*.yaml` to see existing trips. If user mentioned a destination that matches an existing trip, confirm they want a NEW trip (not to update the existing one).

2. Gather trip basics from the user: - **Destination**: Where are they going? City, country, or region. - **Dates**: When? Start and end dates. If flexible, get approximate dates. - **Trip name**: Optional custom name, or generate one (destination + date/purpose).
Be conversational. If they've already mentioned details, don't re-ask.

3. [Read Trip Data Format]: Read the documentation in: `./skills/sauna/[skill_id]/references/travel.trip.format.md`

4. Create the trip file. Generate a slug from the trip name (lowercase, hyphenated).
Initialize the structure: ```yaml trip: name: [their trip name] destination: [destination] dates: start: [start date] end: [end date] status: upcoming
itinerary: [] bookings: flights: [] hotels: [] reservations: [] other: [] budget: currency: [appropriate currency for destination] planned: 0 expenses: [] documents: emergency_contacts: [] notes: '' ```
Write to `./documents/trips/*.yaml` with filename {slug}.yaml

5. Ask if they want to add any initial details now: - Known flights or travel arrangements? - Hotel/accommodation bookings? - Planned activities or must-dos? - Budget they're working with?
Add whatever they share to the appropriate sections. Don't force them to provide everything—they can add more later.

6. Confirm the trip is created. Show a brief summary: - Trip name and destination - Dates - Any bookings/plans added
Let them know they can update anytime by mentioning the trip.