itinerary-builderlisted

Build a day-by-day travel itinerary from a trip brief — each leg anchored on its base and named station, anchors capped to the declared pace, named transit time between consecutive items, geographic clustering so days don't zigzag, days built to the party's stated mobility, transfer days treated as their own day type, a deliberately light arrival day, booking dependencies with lead times, and every time-sensitive claim tagged [verify] instead of asserted. Use when the constraints are known and the output needed is the actual plan. Do NOT use to gather the constraints first (that's trip-brief) or to adversarially review a finished plan (that's itinerary-critique).
sananthanarayan/skilldrop · ★ 2 · AI & Automation · score 73

Install: claude install-skill sananthanarayan/skilldrop

# itinerary-builder Produce a plan that **survives contact with a real day**: the transit is counted, the days are clustered, the arrival day is honest about jet lag, and nothing time-sensitive is asserted as fact. The rule that separates this from a generic list of sights: **you do not know today's opening hours, prices, or availability.** You never did. So this skill states what a place *is* and why it earns a slot, and tags everything that drifts with `[verify]` — turning the plan into something the traveller confirms rather than something they trust and discover at a locked door. ## How to respond 1. **Restate the operating constraints in three lines.** Dates, party and pace from the brief, plus any `[missing]` fields you're building around. If pace wasn't declared, assume **standard (2 anchors/day)** and say so. Cap clarifying questions at 2. 2. **Anchor each leg on its base and its station, and say which station.** Output a short **where you sleep** block per leg — property (or `[missing]`), the area, and the walk to the station you will actually use. Two traps to name explicitly: a city with **two mainline stations** on opposite sides (departing from the wrong one is a missed train), and a town with **two stations** where only one serves your onward trains — anchor on the one everything leaves from and say so. Then give a small **base → key destinations** table: destination · route · rough time. That table is what the traveller actually reads each morning. 3. **C