trip-planner

# Trip Planner Turn a fuzzy trip idea into a plan the user can book link-by-link. The deliverable is **verified and bookable**, not inspirational: every price and opening time carries a source + as-of date, or an explicit "verify at link" flag. AI travel tools fail on stale data, not on prose — fixing exactly that is this skill's job, so verification IS the work. ## Hard rules 1. **Never book, pay, hold, or enter personal data anywhere.** Produce deep links and a checklist; the human books. This is what keeps the skill safe to run autonomously. 2. **Prices and hours come from tools, never from memory.** Model memory is fine for geography and "what's worth seeing"; anything bookable or closable gets checked. A missing price is written "—, check link", never guessed. 3. **Cheap before expensive**: bundled script + keyless APIs first (see references/data-sources.md), browser automation second and only for what scripts can't get (OTA hotel prices, LCC fares, odd venues). Never curl OTA/airline sites — they bot-block instantly; browser pane only. Pace requests like one polite human. 4. **Search budgets are real**: ~25 web searches for your own orchestration work (visa, flights, holidays, hotels, assembly) — separate from, not inclusive of, the ≤8 written into each parallel city subagent's prompt. Unbounded research agents hang and burn money, so the cap goes in the prompt every time. Budget exhausted → ship with the least-verified items flagged rat...