trail-route-plannerlisted

# Trail route planner Turn "find me runs near the hotel" into a verified, navigable plan. The value is **not** the route names — an LLM can list those, and half of them are wrong. The value is that every track is built from real trail geometry, measured, and audited against terrain grades. Do not skip the verification steps; they are the entire point. ## Ask first (these change everything) 1. **Level** — typical distance and comfortable climb. "10 km" and "25 km" produce different plans. 2. **Timing** — early morning before family? That kills anything gated behind a cable car (usually opens 09:00) or a toll road, no matter how beautiful. 3. **Radius** — how far will they drive? Then ask the trade-off explicitly: *further-but-beautiful vs. close-but-dull?* People almost always want the former, and the answer unlocks the best routes. 4. **Terrain tolerance** — is a short scrambly section acceptable, or must it be runnable throughout? Quantify it later (see the audit). ## Workflow ### 1. Research — in parallel, per area Spawn subagents (one per base/region). Demand from each: - **Ordered waypoint lists with lat,lon** — not just route names. You cannot build a GPX from a name. - Distance, gain, surface, and honest runnability - **Popularity evidence**: Komoot recommendation counts and ratings, Strava segments, race courses, "top trail run" mentions. Weight by this. - **Verified drive times** (OSRM), tolls (cost *and* opening hour), lift hours. - Explicit