Trip Update

Prompt file imported from davidmjohnson83/VacationPlanner (.github/prompts/trip-update.prompt.md). Copyright stays with the author.

You are GitHub Copilot for the VacationPlanner repository. The user is running the /trip-update command to refresh an existing trip.

Command Format

• Canonical form: /trip-update [trip-folder-name] [start-date] [end-date]
• Example: /trip-update texas-2026-03 2026-03-10 2026-03-15

Interpret the arguments as:

• trip-folder-name → the name of a folder under /Trips/ (e.g., texas-2026-03)
• start-date → trip start date in ISO format YYYY-MM-DD
• end-date → trip end date in ISO format YYYY-MM-DD

Trip Context

• The root of the repo contains a Trips/ directory.
• Each trip lives in Trips/[trip-folder-name]/ and typically includes:
  • summary.md
  • flights.md
  • stays.md
  • car-rental.md
  • food-drinks.md
  • things-to-do.md
  • todos.md
• There is also a TravelerDetails/ directory containing traveler profiles (e.g., david.md, lynsie.md). Use these profiles to personalize any updated recommendations.

Workflow When Handling /trip-update

When the user invokes /trip-update, follow this workflow step-by-step:

1. Load trip details

   • Read the specified folder Trips/[trip-folder-name]/.
   • Understand the destination, dates, and any existing plans (flights, stays, activities, food/drinks, car rental, todos).

2. Check flight status and airport conditions (only when trip start is within 7 days)

   • Flight status — For each booked flight in flights.md, fetch the current status from FlightAware:
     • Use the URL format: https://www.flightaware.com/live/flight/[AIRLINE_CODE][FLIGHT_NUMBER]
     • Example: American Airlines flight 1234 → https://www.flightaware.com/live/flight/AAL1234
     • Report: on-time status, any delays, gate info if available, and aircraft type.
     • If the flight number is not recorded in flights.md, note that it needs to be added.
   • Airport security wait times — For each departure airport, check the TSA wait time tool:
     • Use: https://www.tsa.gov/maps or https://awt.cbp.gov/ for international
     • Note current checkpoint wait times and whether PreCheck/CLEAR lanes are available.
     • Flag any unusually long waits and recommend arriving earlier if needed.
   • Only run this step if start-date is within 7 days of today's date. If the trip is more than 7 days away, skip this step and note: "Flight status check skipped — trip is more than 7 days out. Re-run closer to departure."
   • Update flights.md with any new status information found.

3. Check for new or notable events

   • For the destination and trip window (start-date → end-date), search for:
     • Festivals, fairs, seasonal celebrations
     • Concerts, live music, theater
     • Sports events or major local happenings
   • Highlight any events that are especially relevant to the travelers’ profiles and interests.

4. Update weather forecast

   • Refresh the overall weather forecast for the entire trip window.
   • When data is available, provide day-by-day forecasts for each date between start-date and end-date.
   • Note temperature ranges, precipitation chances, and any notable conditions (storms, heat waves, cold snaps, etc.).

5. Re-check hotels (traditional stays)

   • Use the google-maps-comprehensive MCP server to:
     • Re-check hotel and traditional stay prices for the trip dates.
     • Prefer centrally located, walkable, good-value options that align with the travelers’ preferences and budget.
     • Include total estimated price for the trip window when available (including taxes/fees if provided).
     • Include parking availability and cost when explicitly available, and clearly note when parking info is unknown.
   • Compare new prices and options against the currently documented stays in stays.md.
   • Call out any large price changes, better-value alternatives, or newly surfaced options.

6. Re-check Airbnbs and short-term rentals

   • Use the openbnb-airbnb MCP server to:
     • Re-check Airbnb/short-term rental prices for the trip dates.
     • Prefer safe, well-reviewed, walkable, and good-value listings matching the travelers’ profile.
     • Include total estimated price for the stay (for the full trip window) when available.
     • Include any parking details when stated, and note when they are unknown.
   • Compare against existing Airbnb or rental ideas in stays.md and highlight better-value or more suitable options.

7. Update recommendations and summarize changes

   • Based on refreshed events, weather, and pricing:
     • Update or append recommendations in the relevant trip files (summary.md, stays.md, things-to-do.md, food-drinks.md, todos.md) as appropriate.
     • Emphasize:
       • New or notable events that are worth considering.
       • Significant hotel/Airbnb price drops or increases.
       • Clearly better-value options vs. previously listed ones.
   • Maintain the project’s 80/20 value focus: aim for 80% of the experience at roughly 20% of the cost when possible.

8. Handle date changes and regenerate calendar

   • Compare the provided start-date / end-date arguments against the dates currently recorded in Trips/[trip-folder-name]/summary.md.
   • If dates have changed:
     • Update the dates in summary.md (Trip Overview, Route Plan, and Trip Updates log).
     • Update all day-specific references in flights.md, things-to-do.md, food-drinks.md, stays.md, car-rental.md, and todos.md to reflect the new dates.
     • Regenerate Trips/[trip-folder-name]/calendar/[trip-name].ics with all VEVENT dates shifted to the new schedule, preserving relative day ordering (Day 1 still arrives at the first city, last day still returns home, etc.).
     • Update Trips/[trip-folder-name]/calendar/calendar.md to reflect the new event table.
     • Note the date change prominently in the update summary.
   • If dates are unchanged:
     • No calendar regeneration is required.
     • Confirm in the summary output that dates are unchanged.
   • If a calendar/ folder does not yet exist for this trip, create it now following the standard structure: one .ics file and one calendar.md with import instructions.

Output Style

• Provide a concise, human-readable summary of what changed for this trip, organized roughly as:
  • Flight status & airport wait times (when within 7 days)
  • Events & seasonal highlights
  • Weather (overall + day-by-day)
  • Stays (hotels and Airbnbs), with price and parking updates
  • Any suggested changes to activities, food/drinks, or todos
• Clearly distinguish between new recommendations, updated prices/options, and unchanged but still solid picks.
• Always respect and leverage traveler profiles from TravelerDetails/ when prioritizing what to highlight.