plan-hiking-tour
À propos
Cette compétence aide les développeurs à planifier des randonnées en sélectionnant des sentiers selon les cotes de difficulté SAC/UIAA et en estimant les temps de marche précis à l'aide de la formule de Munter. Elle analyse le dénivelé, évalue la sécurité et gère la logistique pour les randonnées à la journée comme pour les itinéraires de plusieurs jours en refuge. Utilisez-la lors de la création d'applications nécessitant de générer des itinéraires de randonnée adaptés à la condition physique et au niveau d'expérience d'un groupe.
Installation rapide
Claude Code
Recommandénpx skills add pjt222/agent-almanac -a claude-code/plugin add https://github.com/pjt222/agent-almanacgit clone https://github.com/pjt222/agent-almanac.git ~/.claude/skills/plan-hiking-tourCopiez et collez cette commande dans Claude Code pour installer cette compétence
Documentation
Plan Hiking Tour
Plan hiking tour. Select trails, estimate times, analyze elevation, assess safety. For groups of varying fitness levels.
When Use
- Planning day hike or multi-day trekking tour
- Selecting trails fitting group fitness and experience
- Estimating realistic hiking times for route planning
- Assessing if route safe given current conditions
- Planning hut-to-hut tours with overnight logistics
Inputs
- Required: Region or area for hike
- Required: Group profile (people count, fitness level, experience)
- Required: Available time (day hike duration or days count)
- Optional: Difficulty preference (SAC T1-T6, or descriptive: easy/moderate/hard)
- Optional: Elevation gain/loss tolerance (meters)
- Optional: Specific peaks, huts, destinations to include
- Optional: Season and expected weather window
Steps
Step 1: Define Requirements
Set parameters that constrain trail selection.
Group Fitness Classification:
┌──────────────┬──────────────────────────────────────────────────┐
│ Level │ Capabilities │
├──────────────┼──────────────────────────────────────────────────┤
│ Beginner │ 3-4 hrs walking, <500 m elevation gain, │
│ │ well-marked paths only (SAC T1-T2) │
├──────────────┼──────────────────────────────────────────────────┤
│ Intermediate │ 5-7 hrs walking, 500-1000 m elevation gain, │
│ │ mountain trails with some exposure (SAC T2-T3) │
├──────────────┼──────────────────────────────────────────────────┤
│ Advanced │ 7-10 hrs walking, 1000-1500 m elevation gain, │
│ │ alpine trails, scrambling (SAC T3-T5) │
├──────────────┼──────────────────────────────────────────────────┤
│ Expert │ 10+ hrs, 1500+ m gain, via ferrata, glacier, │
│ │ technical terrain (SAC T5-T6, UIAA I-III) │
└──────────────┴──────────────────────────────────────────────────┘
SAC Hiking Scale Reference:
T1 - Hiking: Well-maintained paths, no exposure
T2 - Mountain hiking: Marked trails, some steep sections
T3 - Demanding: Exposed sections, scree, basic scrambling
T4 - Alpine hiking: Simple scrambling, steep exposed terrain
T5 - Demanding alpine: Challenging scrambling, glacier crossings
T6 - Difficult alpine: Very exposed climbing, technical ice/rock
Document group's weakest-link fitness — sets max difficulty.
Got: Clear requirements profile — group level, time budget, elevation tolerance, must-include or must-avoid constraints.
If fail: Group has mixed fitness levels? Plan for weakest member. Identify optional extensions for stronger hikers (e.g. peak side trip while others rest at hut).
Step 2: Select Trail Candidates
Research and shortlist trails matching requirements.
Sources for trail data:
- Hiking guidebooks and regional websites
- OpenStreetMap (trails tagged with
sac_scale) - National/regional trail databases (e.g. SchweizMobil, Alpenverein)
- WebSearch for "[region] hiking trails [difficulty]"
For each candidate trail, collect:
Trail Data Sheet:
┌─────────────────────┬──────────────────────────────────────┐
│ Field │ Value │
├─────────────────────┼──────────────────────────────────────┤
│ Trail name/number │ │
│ Start point │ Name, elevation, access │
│ End point │ Name, elevation, access │
│ Distance (km) │ │
│ Elevation gain (m) │ │
│ Elevation loss (m) │ │
│ Highest point (m) │ │
│ Difficulty (SAC) │ │
│ Exposure │ None / Moderate / Significant │
│ Markings │ Well-marked / Sparse / Unmarked │
│ Huts/shelters │ Names and locations along route │
│ Water sources │ Reliable / Seasonal / None │
│ Season │ Months when passable │
│ Escape routes │ Points where you can exit early │
└─────────────────────┴──────────────────────────────────────┘
Shortlist 2-3 candidates fitting requirements plus one easier backup.
Got: Shortlist of trail candidates with complete data sheets — all within group capability range.
If fail: No trails match all constraints? Relax least important constraint first (usually distance before difficulty). Trail data incomplete? Note gaps. Plan to verify on-site or contact local tourism offices.
Step 3: Calculate Times Using Munter Formula
Estimate hiking time with Swiss Alpine Club (SAC) Munter formula for realistic planning.
Munter Formula:
Time (hours) = (horizontal_km + vertical_km) / pace
Where:
- horizontal_km = trail distance in km
- vertical_km = elevation gain in meters / 100
(each 100 m up counts as 1 km)
- pace = km/h achieved on flat ground
Pace by Fitness Level:
┌──────────────┬────────────────┬──────────────────────────────┐
│ Level │ Pace (km/h) │ Notes │
├──────────────┼────────────────┼──────────────────────────────┤
│ Beginner │ 3.5 │ Includes frequent stops │
│ Intermediate │ 4.0 │ Steady pace, short breaks │
│ Advanced │ 4.5 │ Efficient pace, few breaks │
│ Expert │ 5.0 │ Fast and steady │
│ With kids │ 2.5-3.0 │ Very frequent stops │
│ Heavy pack │ Subtract 0.5 │ Multi-day with full pack │
└──────────────┴────────────────┴──────────────────────────────┘
Descent Adjustment:
- Gentle descent (<20% grade): adds minimal time
- Steep descent (>20% grade): add elevation_loss_m / 200 hours
- Very steep/technical: add elevation_loss_m / 150 hours
Example calculation:
Trail: 12 km distance, 850 m elevation gain, 400 m steep descent
Group: Intermediate (pace = 4.0 km/h)
Ascent component: (12 + 850/100) / 4.0 = (12 + 8.5) / 4.0 = 5.1 hours
Descent component: 400 / 200 = 2.0 hours additional for steep descent
Total estimate: 5.1 + 2.0 = 7.1 hours (round to 7-7.5 hours)
Add breaks: +30 min lunch, +15 min x 3 short breaks = +75 min
Total with breaks: approximately 8.5 hours trailhead to trailhead
Got: Time estimates per trail candidate — includes break time. Estimates conservative (better arrive early than hike in dark).
If fail: Calculated times exceed daylight? Route too long. Shorten (closer end point or skip section via transport) or split into two days. Group untested? Use beginner pace day one, adjust based on actual performance.
Step 4: Assess Safety
Evaluate objective and subjective hazards for selected route.
Safety Assessment Checklist:
┌──────────────────────┬────────────┬──────────────────────────────┐
│ Hazard │ Rating │ Mitigation │
├──────────────────────┼────────────┼──────────────────────────────┤
│ Weather forecast │ Good/Fair/ │ Check 3 sources; define │
│ │ Poor │ turn-around weather triggers │
├──────────────────────┼────────────┼──────────────────────────────┤
│ Thunderstorm risk │ Low/Med/ │ Plan to be below treeline │
│ │ High │ by early afternoon │
├──────────────────────┼────────────┼──────────────────────────────┤
│ Snow/ice on trail │ None/Some/ │ Check snow line; carry │
│ │ Extensive │ microspikes if needed │
├──────────────────────┼────────────┼──────────────────────────────┤
│ River crossings │ Dry/Normal/│ Check recent rainfall; │
│ │ High water │ identify bridges or fords │
├──────────────────────┼────────────┼──────────────────────────────┤
│ Exposure/fall risk │ None/Mod/ │ Assess group comfort level; │
│ │ Significant│ carry slings for short-roping│
├──────────────────────┼────────────┼──────────────────────────────┤
│ Trail condition │ Good/Fair/ │ Check maintenance reports; │
│ │ Poor │ plan for slower pace if poor │
├──────────────────────┼────────────┼──────────────────────────────┤
│ Escape routes │ Multiple/ │ Identify exit points and │
│ │ Few/None │ nearest road access │
├──────────────────────┼────────────┼──────────────────────────────┤
│ Cell coverage │ Good/Spotty│ Download offline maps; │
│ │ /None │ carry emergency beacon if │
│ │ │ remote │
└──────────────────────┴────────────┴──────────────────────────────┘
Overall Safety Rating:
GREEN - All factors favorable, proceed as planned
YELLOW - One or more concerns, proceed with extra caution and backup plan
RED - Significant hazards present, postpone or choose alternative route
Got: Completed safety assessment — all hazards rated, mitigations documented. GREEN/YELLOW/RED rating for go/no-go.
If fail: Assessment yields RED for primary route? Switch to backup from Step 2. All options RED (e.g. severe weather)? Postpone hike. NEVER override RED safety rating for schedule convenience.
Step 5: Plan Logistics
Organize practical details for hiking day or multi-day tour.
Logistics Checklist:
┌──────────────────────┬──────────────────────────────────────────┐
│ Category │ Details to confirm │
├──────────────────────┼──────────────────────────────────────────┤
│ Trailhead access │ Driving directions, parking, bus/train │
│ Hut reservations │ Booking required? Half-board available? │
│ Water resupply │ Reliable sources along route │
│ Food │ Packed lunch, hut meals, snacks │
│ Gear │ See check-hiking-gear skill │
│ Emergency contacts │ Mountain rescue #, local emergency │
│ Map and navigation │ Paper map, offline GPS, waypoints loaded │
│ Group communication │ Meeting points if group separates │
│ Return transport │ Last bus/train time from endpoint │
│ Parking shuttle │ If start != end, how to retrieve car │
└──────────────────────┴──────────────────────────────────────────┘
For multi-day tours:
- Book huts well in advance (popular huts fill months ahead)
- Plan resupply points for food and water
- Identify bail-out points for each day (where to exit if injured or weather turns)
- Share itinerary with someone not on hike
Got: All logistics confirmed or flagged pending. Hut reservations made. Transport to/from trailhead arranged. Emergency plan documented.
If fail: Huts full? Check nearby alternatives (bivouacs, camping, lower huts with longer approach). Trailhead access complicated (e.g. closed road)? Arrange alternative transport or adjust starting point.
Step 6: Generate Hiking Plan
Compile everything into complete hiking plan document.
Hiking Plan Document Structure:
1. Summary
- Route name, dates, total distance/elevation
- Group members and emergency contacts
- Overall difficulty and safety rating
2. Day-by-Day Itinerary
- Start/end points with times
- Distance, elevation gain/loss, estimated time
- Key waypoints and navigation notes
- Water sources and meal plans
- Escape route options
3. Safety Information
- Weather forecast (to be updated day-of)
- Known hazards and mitigations
- Turn-around time and triggers
- Emergency procedures and contacts
4. Logistics
- Transport arrangements
- Accommodation bookings
- Gear checklist reference
5. Maps
- Overview map with all days
- Elevation profile for each day
Got: Complete hiking plan — share with all participants, leave copy with emergency contact. Plan actionable without additional research.
If fail: Plan has gaps that can't be filled before departure? Document them clearly. Assign someone to resolve each item. Critical safety gaps (no escape route identified, no weather check plan) MUST be resolved before departure.
Checks
- Trail difficulty matches group's fitness and experience level
- Time estimates use Munter formula with appropriate pace for group
- Safety assessment completed — all hazards rated
- Overall safety rating GREEN or YELLOW (not RED)
- Hut/accommodation reservations confirmed for multi-day tours
- Water resupply points identified for each segment
- Escape routes mapped for each day
- Emergency contacts and procedures documented
- Itinerary shared with emergency contact not on hike
- Gear checklist generated (via check-hiking-gear skill)
Pitfalls
- Plan for fastest hiker: Always plan for slowest group member. Group moves at pace of weakest link.
- Ignore descent time: Steep descents slow and punishing on knees. Munter formula accounts for this — many hikers underestimate.
- No turnaround time: Set hard turnaround time (usually early afternoon for alpine routes). Avoid descending in darkness or afternoon thunderstorms.
- Skip backup route: Weather and conditions change. Always have easier alternative ready.
- Overloaded first day: Start with shorter, easier day to assess group pace and acclimatize — especially at altitude.
- Altitude underestimation: Above 2500 m, reduce pace 10-20% for unacclimatized hikers. Above 3000 m, altitude sickness risk real.
- Hut booking assumptions: Popular mountain huts (especially Alps) need reservations weeks or months ahead. NEVER assume walk-in availability in high season.
See Also
check-hiking-gear— generate optimized gear checklist for planned hikeassess-trail-conditions— evaluate current conditions on selected trailplan-tour-route— broader tour planning for non-hiking segmentscreate-spatial-visualization— visualize hiking route and elevation profilegenerate-tour-report— compile hiking plan into formatted report
Dépôt GitHub
Compétences associées
executing-plans
DesignUtilisez la compétence executing-plans lorsque vous disposez d'un plan de mise en œuvre complet à exécuter par lots contrôlés avec des points de contrôle de revue. Elle charge et examine le plan de manière critique, puis exécute les tâches par petits lots (3 tâches par défaut) tout en rapportant la progression entre chaque lot pour une revue par l'architecte. Cela garantit une mise en œuvre systématique avec des points de contrôle de qualité intégrés.
requesting-code-review
DesignCette compétence délègue un sous-agent réviseur de code pour analyser les modifications apportées au code par rapport aux exigences avant de poursuivre. Elle doit être utilisée après avoir terminé des tâches, implémenté des fonctionnalités majeures, ou avant une fusion vers la branche principale. La revue aide à détecter précocement les problèmes en comparant l'implémentation actuelle avec le plan initial.
connect-mcp-server
DesignCette compétence fournit un guide complet permettant aux développeurs de connecter des serveurs MCP à Claude Code via les transports HTTP, stdio ou SSE. Elle couvre l'installation, la configuration, l'authentification et la sécurité pour intégrer des services externes tels que GitHub, Notion et des API personnalisées. Utilisez-la lors de la configuration d'intégrations MCP, de la configuration d'outils externes ou du travail avec le Protocole de Contexte de Modèle de Claude.
web-cli-teleport
DesignCette compétence aide les développeurs à choisir entre les interfaces Web et CLI de Claude Code en fonction de l'analyse des tâches, puis permet une téléportation transparente des sessions entre ces environnements. Elle optimise le flux de travail en gérant l'état et le contexte de la session lors du passage entre le web, la CLI ou le mobile. Utilisez-la pour des projets complexes nécessitant différents outils à diverses étapes.
