← Vacation Planner ProCONTENT HISTORY

Update to Vacation Planner Pro

Snapshot Sep 30, 2026 · 23:16 UTC · version 1.4.0

Collection source: not recorded for this historical snapshot.

WHAT CHANGED · RULE-BASED ANALYSIS

First saved snapshot

No earlier snapshot is available to establish a change.

Compare saved observations

Download comparison JSON
Full technical diff · 0 changed fields
Full snapshot data
{
  "description": "Design or repair a geographically coherent multi-day itinerary with realistic transfers, pacing, opening-day constraints, downtime, and weather alternatives. Use for focused routing requests or when explicitly invoked as a research track. For a complete trip, return route analysis to vacation-planner.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 264
    },
    {
      "relative_path": "references/routing-standards.md",
      "size_in_bytes": 847
    }
  ],
  "name": "route-itinerary",
  "skill_md_contents": "---\nname: route-itinerary\ndescription: Design or repair a geographically coherent multi-day itinerary with realistic transfers, pacing, opening-day constraints, downtime, and weather alternatives. Use for focused routing requests or when explicitly invoked as a research track. For a complete trip, return route analysis to vacation-planner.\n---\n\n# Route and Itinerary\n\nBuild around arrival/departure reality, then choose the fewest bases that preserve the experience. Read [routing-standards.md](references/routing-standards.md).\n\nMap each candidate by geography, opening day, duration, energy, reservation pressure, and weather dependence. Count door-to-door transfer time, not scheduled vehicle time alone. Treat a long transfer, major hike, full-day boat trip, or national-park excursion as the day's anchor.\n\nDefault each day to one anchor, one complementary activity, meal space, and a flex option. Follow demanding days with lighter time. Keep the first and last days conservative. Do not add stops solely because they fit on a map.\n\nReturn the recommended route, rejected alternatives and why, a day-by-day sequence, transfer assumptions, schedule dependencies, and contingency swaps.\n\nWhen driving comfort matters, capture maximum daily wheel time, road width/class tolerance, mountain or cliff exposure, night-driving tolerance, parking needs, transmission requirement, and one-way rental constraints. Give every road transfer a friction note rather than relying on distance alone.\n\nFor hikes capture distance, ascent, expected duration, surface, exposure, navigation, seasonal/weather risk, official status/source, parking or shuttle logistics, bailout options, and an indoor or lowland substitute. Ask for comfortable distance, ascent, and exposure when they would change the route.\n"
}

SHA-256 of public snapshot: bb8b13e1427e0845b7b44383053fa83a5c27c447b6eebeb0a66d2783a60986a5