travel-planning

Dieser Auszug wurde bei der Prüfung gespeichert. Die externe Quelle enthält die vollständige und aktuelle Version.

---
name: travel-planning
version: 1.2.0
description: Plan trips, build itineraries, research destinations, estimate budgets, and organize logistics for Mick's travel. Always trigger immediately when the user mentions planning a trip, asks about flights, hotels, itineraries, destinations, or uses phrases like "trip to", "travel to", "planning a visit", "what should I do in", "how do I get to", "how much will this cost", or references any upcoming travel. Also trigger when the user mentions specific destinations, asks about visa requirements, crossing borders, ferry routes, or comparing travel options. This skill encodes Mick's full travel preferences and constraints so outputs are personalized from the first message — never produce generic travel advice.
---

# Travel Planning Skill

## Intent

Plan solo travel with destination fit, logistics, budget, preferences, booking triage, and itinerary handoff.

## Use When

- The user explicitly asks for `travel-planning`.
- The request matches the triggers or workflow described below.
- The task benefits from a reusable, structured output instead of a one-off answer.

## Do Not Use When

- Do not use for live booking, legal visa advice, medical travel advice, or broad research better handled by travel-research.
- Required context is missing and cannot be reasonably inferred.
- A more specific skill in this repo is a better match.

## Workflow

1. Identify the exact task and available source material.
2. Apply the domain rules and output format in this skill.
3. State assumptions, uncertainty, and missing inputs clearly.
4. Return the requested artifact, recommendation, or review in a practical format.
5. Check the result against the validation checklist before finishing.

Produces personalized, opinionated travel plans for Mick Pletcher. Every output should reflect his specific constraints and preferences — never produce generic tourist recommendations.

---

## Who This Is For

**Mick Pletcher** — Automation Engineer, endurance athlete, and adventure traveler based in Nashville, TN. Visited 33+ countries, targeting 50. Summited Kilimanjaro. Background in competitive cycling and triathlon. Pursues geographic arbitrage and early retirement.

**Travel style: Solo by default.** All itineraries, budgets, and logistics are planned for one person unless Mick explicitly states otherwise. Do not suggest group tours, couples packages, or shared activities framed for multiple people. When Mick mentions a travel companion for a specific trip, note it and adjust accordingly but do not assume it carries over to other trips.

---

## Hard Constraints (Never Violate)

| Constraint | Rule |
|---|---|
| Accommodation | **Private rooms only** — no dorms, no shared baths |
| Home Airport | **BNA (Nashville)** — all flights route through BNA unless Mick specifies otherwise |
| Budget mindset | Value-optimized, not budget-backpacker and not luxury — target the best experience per dollar |
| Activities | Anchor the trip around an **endurance or adventure activity** when one is available (cycling, hiking, running events, climbing, skydiving, etc.) |
| Geographic arbitrage | Flag when a destination offers strong USD value — eating, accommodation, transport costs |

---

## Travel Preferences

**Accommodation style**: Boutique hotels, guesthouses, locally-owned properties. Avoid large chain hotels unless price/location is overwhelming.

**Pace**: Active and structured, not leisurely. Mick covers a lot of ground. Plan for full days.

**Food**: Street food and local spots over tourist restaurants. No dietary restrictions.

**Transport**: Train or ferry over flying when it's feasible and interesting. Renting a car is fine for rural/off-grid destinations.

**Experiences over things**: Prioritize events, physical challenges, cultural immersion over museums and shopping.

**Social media documentation**: Mick documents trips publicly on Facebook an