route-plannerlisted

Turn an origin, destination, and dates into a day-by-day driving route. Trigger when the user asks to plan a road trip ("plan a road trip from Chicago to Denver"), when a new trip folder is being created, or when an existing trips/<trip>/trip.md has an empty or tentative Route section. Reads profiles/travelers.md for driving limits, motion sickness, and who can share driving, and trip.md Parameters for dates and style. Proposes a fastest option plus 1-2 scenic options built around stops matched to the travelers' interests, each stated with total drive time, tolls, notable-stop facts, and food picks along the way, then writes the chosen route (per-day segments, decision date) and rejected options (with reason) back into trip.md.
skandm/trip-planner-template · ★ 0 · API & Backend · score 72

Install: claude install-skill skandm/trip-planner-template

# Route planner This skill turns a trip request into a concrete route split across driving days, respecting who's actually in the car. ## Step 1: Read before asking 1. Read `profiles/travelers.md`. If missing or `status: template`, invoke the **traveler-profiles** skill first — route pacing depends on daily driving limits, motion sickness, and who can drive. Also note the party's stated Interests here (history, nature, food, quirky roadside stuff, etc.) — this is what should steer *which* stops a scenic option is built around, not a generic "pretty road." 2. Read (or create) `trips/<trip-name>/trip.md`. If the Parameters section already has origin, destination, dates, vehicle, and style, don't re-ask — confirm briefly instead ("scenic over fast, arrive by the 17th evening — still right?"). 3. Only ask the user for what's genuinely missing: origin, destination, date range, any hard arrival deadline, style preference (scenic vs. fast, interstates okay or not, stops per day), and — if travelers.md has no Interests to go on — what kind of stops would make a detour worth it (nature, history, food, oddities). 4. **Running outside the repo** (e.g. a claude.ai chat with nothing attached, no `trip.md` path available) — there's no trip folder to read or create. Gather the same parameters conversationally (origin, destination, dates, style, deadline, interests), ask the user to attach their `travelers.md` if they have one, or run the traveler-profiles interview inline if they want pr