replannerlisted

# Replanner This skill adjusts a trip already underway, changing as little as possible. ## Step 1: Read the file as ground truth Read `trips/<trip>/trip.md` fresh — don't rely on what you remember from earlier in the conversation. The user may have hand-edited it on the road (a stay they booked themselves, a day they already skipped); per workspace conventions, the file wins over conversation memory whenever they conflict. Also read `profiles/travelers.md` — hard constraints and logistics don't change just because plans did. **Running outside the repo** (e.g. a claude.ai chat with no files attached) — ask the user to attach their `trip.md`; it's this skill's explicit ground truth, so there's nothing to diff against without it. Carry through the same process below, then in Step 5, instead of writing to disk, output the full updated file content back as a fenced markdown block for the user to save over their own copy. ## Step 2: Scope the disruption precisely Identify exactly which days/segments the disruption touches. A road closure affects the segments using that road; fatigue affects tomorrow's drive block, not the whole trip; a cancelled hotel affects one night's Stays entry. Everything outside that scope must stay byte-for-byte identical — this is a minimal-diff operation, not a re-plan from scratch. ## Step 3: Recompute only the affected part - **Route changes** — reuse the constraint-deriving and option-proposing approach from **route-planner** (daily driving li