plan-hiking-tour

Plan a hiking tour with trail selection by difficulty (SAC/UIAA), time estimation using Munter's formula, elevation analysis, and safety assessment. Covers multi-day hut-to-hut tours, day hikes, and alpine routes with terrain classification and group fitness considerations. Use when planning a day hike or multi-day trekking tour, selecting trails appropriate for a group's fitness and experience, estimating realistic hiking times, or planning hut-to-hut tours with overnight logistics.

9 stars

Best use case

plan-hiking-tour is best used when you need a repeatable AI agent workflow instead of a one-off prompt.

Plan a hiking tour with trail selection by difficulty (SAC/UIAA), time estimation using Munter's formula, elevation analysis, and safety assessment. Covers multi-day hut-to-hut tours, day hikes, and alpine routes with terrain classification and group fitness considerations. Use when planning a day hike or multi-day trekking tour, selecting trails appropriate for a group's fitness and experience, estimating realistic hiking times, or planning hut-to-hut tours with overnight logistics.

Teams using plan-hiking-tour should expect a more consistent output, faster repeated execution, less prompt rewriting.

When to use this skill

  • You want a reusable workflow that can be run more than once with consistent structure.

When not to use this skill

  • You only need a quick one-off answer and do not need a reusable workflow.
  • You cannot install or maintain the underlying files, dependencies, or repository context.

Installation

Claude Code / Cursor / Codex

$curl -o ~/.claude/skills/plan-hiking-tour/SKILL.md --create-dirs "https://raw.githubusercontent.com/pjt222/agent-almanac/main/i18n/caveman-lite/skills/plan-hiking-tour/SKILL.md"

Manual Installation

  1. Download SKILL.md from GitHub
  2. Place it in .claude/skills/plan-hiking-tour/SKILL.md inside your project
  3. Restart your AI agent — it will auto-discover the skill

How plan-hiking-tour Compares

Feature / Agentplan-hiking-tourStandard Approach
Platform SupportNot specifiedLimited / Varies
Context Awareness High Baseline
Installation ComplexityUnknownN/A

Frequently Asked Questions

What does this skill do?

Plan a hiking tour with trail selection by difficulty (SAC/UIAA), time estimation using Munter's formula, elevation analysis, and safety assessment. Covers multi-day hut-to-hut tours, day hikes, and alpine routes with terrain classification and group fitness considerations. Use when planning a day hike or multi-day trekking tour, selecting trails appropriate for a group's fitness and experience, estimating realistic hiking times, or planning hut-to-hut tours with overnight logistics.

Where can I find the source code?

You can find the source code on GitHub using the link provided at the top of the page.

SKILL.md Source

# Plan Hiking Tour

Plan a hiking tour with trail selection, time estimation, elevation analysis, and safety assessment for groups of varying fitness levels.

## When to Use

- Planning a day hike or multi-day trekking tour
- Selecting trails appropriate for a group's fitness and experience
- Estimating realistic hiking times for route planning
- Assessing whether a route is safe given current conditions
- Planning hut-to-hut tours with overnight logistics

## Inputs

- **Required**: Region or area for the hike
- **Required**: Group profile (number of people, fitness level, experience)
- **Required**: Available time (day hike duration or number of days)
- **Optional**: Difficulty preference (SAC T1-T6, or descriptive: easy/moderate/hard)
- **Optional**: Elevation gain/loss tolerance (meters)
- **Optional**: Specific peaks, huts, or destinations to include
- **Optional**: Season and expected weather window

## Procedure

### Step 1: Define Requirements

Establish the 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 the group's weakest-link fitness level, as this determines the maximum difficulty.

**Got:** A clear requirements profile with group level, time budget, elevation tolerance, and any must-include or must-avoid constraints.

**If fail:** If the group has mixed fitness levels, plan for the weakest member but identify optional extensions for stronger hikers (e.g., a peak side trip while others rest at a hut).

### Step 2: Select Trail Candidates

Research and shortlist trails matching the 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 that fit the requirements plus one easier backup option.

**Got:** A shortlist of trail candidates with complete data sheets, all within the group's capability range.

**If fail:** If no trails match all constraints, relax the least important constraint first (typically distance before difficulty). If trail data is incomplete, note the gaps and plan to verify on-site or contact local tourism offices.

### Step 3: Calculate Times Using Munter Formula

Estimate hiking time using the 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 for each trail candidate, including break time. Estimates should be conservative (better to arrive early than to hike in darkness).

**If fail:** If calculated times exceed the available daylight, the route is too long. Either shorten it (find a closer end point or skip a section via transport) or split into two days. If the group is untested, use the beginner pace for the first day and adjust based on actual performance.

### Step 4: Assess Safety

Evaluate objective and subjective hazards for the 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:** A completed safety assessment with all hazards rated and mitigations documented. An overall GREEN/YELLOW/RED rating for the go/no-go decision.

**If fail:** If the assessment yields RED for the primary route, switch to the backup option from Step 2. If all options are RED (e.g., severe weather forecast), postpone the hike. Never override a RED safety rating for schedule convenience.

### Step 5: Plan Logistics

Organize practical details for the 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:
1. Book huts well in advance (popular huts fill months ahead)
2. Plan resupply points for food and water
3. Identify bail-out points for each day (where to exit if someone is injured or weather turns)
4. Share the itinerary with someone not on the hike

**Got:** All logistics confirmed or flagged as pending. Hut reservations made. Transport to/from trailhead arranged. Emergency plan documented.

**If fail:** If huts are full, check for nearby alternatives (bivouacs, camping, lower huts with longer approach). If trailhead access is complicated (e.g., closed road), arrange alternative transport or adjust the starting point.

### Step 6: Generate Hiking Plan

Compile everything into a 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:** A complete hiking plan that can be shared with all participants and left with an emergency contact. The plan should be actionable without additional research.

**If fail:** If the plan has gaps that cannot be filled before departure, document them clearly and assign someone to resolve each item. Critical safety gaps (no escape route identified, no weather check plan) must be resolved before departure.

## Validation

- [ ] Trail difficulty matches the group's fitness and experience level
- [ ] Time estimates use Munter formula with appropriate pace for the group
- [ ] Safety assessment is completed with all hazards rated
- [ ] Overall safety rating is GREEN or YELLOW (not RED)
- [ ] Hut/accommodation reservations are confirmed for multi-day tours
- [ ] Water resupply points are identified for each segment
- [ ] Escape routes are mapped for each day
- [ ] Emergency contacts and procedures are documented
- [ ] Itinerary shared with an emergency contact not on the hike
- [ ] Gear checklist generated (via check-hiking-gear skill)

## Pitfalls

- **Planning for the fastest hiker**: Always plan for the slowest group member. The group moves at the pace of its weakest link.
- **Ignoring descent time**: Steep descents are slow and punishing on knees. The Munter formula accounts for this, but many hikers underestimate it.
- **No turnaround time**: Set a hard turnaround time (typically early afternoon for alpine routes) to avoid descending in darkness or afternoon thunderstorms.
- **Skipping the backup route**: Weather and conditions change. Always have an easier alternative prepared.
- **Overloaded first day**: Start with a shorter, easier day to assess group pace and acclimatize, especially at altitude.
- **Altitude underestimation**: Above 2500 m, reduce pace by 10-20% for unacclimatized hikers. Above 3000 m, altitude sickness risk is real.
- **Hut booking assumptions**: Popular mountain huts (especially in the Alps) require reservations weeks or months in advance. Never assume walk-in availability in high season.

## Related Skills

- `check-hiking-gear` — generate an optimized gear checklist for the planned hike
- `assess-trail-conditions` — evaluate current conditions on the selected trail
- `plan-tour-route` — broader tour planning for non-hiking segments
- `create-spatial-visualization` — visualize the hiking route and elevation profile
- `generate-tour-report` — compile the hiking plan into a formatted report

Related Skills

plan-tour-route

9
from pjt222/agent-almanac

Plan a multi-stop tour route with waypoint optimization, drive/walk time estimation, and POI discovery along the route using OSM data. Covers geocoding, nearest-neighbor and TSP-based ordering, time/distance matrix calculation, and itinerary generation with points of interest. Use when planning a road trip or walking tour with multiple destinations, optimizing visit order to minimize travel time, discovering sites along a route, or comparing driving versus walking versus public transport options.

plan-sprint

9
from pjt222/agent-almanac

Plan a sprint by refining backlog items, defining a sprint goal, calculating team capacity, selecting items, and decomposing them into tasks. Produces a SPRINT-PLAN.md with goal, selected items, task breakdown, and capacity allocation. Use when starting a new sprint in a Scrum or agile project, re-planning after significant scope change, transitioning from ad-hoc work to structured sprint cadence, or after backlog grooming when items are ready for inclusion.

plan-spectroscopic-analysis

9
from pjt222/agent-almanac

Plan a comprehensive spectroscopic analysis campaign by defining the analytical question, assessing sample characteristics, selecting appropriate techniques using a decision matrix, planning sample preparation for each technique, sequencing analyses from non-destructive to destructive, and defining success criteria with a cross-validation strategy.

plan-release-cycle

9
from pjt222/agent-almanac

Plan a software release cycle with milestones, feature freezes, release candidates, and go/no-go criteria. Covers calendar-based and feature-based release strategies. Use when starting planning for a major or minor version release, transitioning from ad-hoc to structured release cadence, coordinating a release across multiple teams or components, defining quality gates for a regulated project, or planning the first public release (v1.0.0) of a project.

plan-garden-calendar

9
from pjt222/agent-almanac

Plan garden activities using solar, lunar, and biodynamic calendars. Covers USDA hardiness zones, frost date calculation, equinox/solstice anchoring, synodic lunar cycle (waxing/waning), ascending/descending moon, Maria Thun biodynamic calendar (root/leaf/flower/fruit days), succession planting schedules, and seasonal task planning. Use when planning a new growing season and needing a planting schedule, integrating lunar or biodynamic timing into garden practice, calculating frost dates and planting windows for a specific zone, setting up succession planting for continuous harvest, or conducting end-of-season review.

plan-eu-relocation

9
from pjt222/agent-almanac

Plan a complete EU/DACH relocation timeline with dependency mapping between bureaucratic steps, deadline tracking, and country-specific procedure identification. Use when planning a move between EU/DACH countries, relocating from a non-EU country to an EU/DACH destination, coordinating employment-based relocation with employer HR, managing a relocation with tight deadlines, or when needing a single document that maps the entire relocation process end-to-end.

plan-capacity

9
from pjt222/agent-almanac

Perform capacity planning using historical metrics and growth models. Use predict_linear for forecasting, identify resource constraints, calculate headroom, and recommend scaling actions before saturation. Use before seasonal traffic spikes or product launches, during quarterly capacity reviews, when resource utilization trends upward, or before budget planning cycles.

generate-tour-report

9
from pjt222/agent-almanac

Generate a Quarto-based tour report with embedded maps, daily itineraries, logistics tables, and accommodation/transport details. Produces a self-contained HTML or PDF document suitable for offline use during travel. Use when compiling a planned tour into a shareable document, creating an offline-accessible travel guide, documenting a completed trip with photos and statistics, or producing a professional tour proposal for a group or client.

forage-plants

9
from pjt222/agent-almanac

Identify and safely gather edible and useful wild plants. Covers safety rules and deadly plant recognition, habitat reading, multi-feature identification methodology, the universal edibility test, sustainable harvesting practices, preparation methods, reaction monitoring, and building knowledge with beginner-friendly universal species. Use when supplementing food supply in a wilderness or survival setting, needing medicinal or utility plants, identifying plants around camp for safety, or in long-term scenarios where foraging extends available rations.

check-hiking-gear

9
from pjt222/agent-almanac

Generate and verify a hiking gear checklist optimized for season, duration, difficulty, and group size with weight management. Covers the ten essentials, layering systems, navigation tools, emergency kit, and group gear distribution. Use when preparing for a day hike or multi-day trekking tour, packing for a group and distributing shared gear, adapting a standard gear list to specific conditions, reviewing gear before departure, or managing pack weight for long or technical routes.

skill-name-here

9
from pjt222/agent-almanac

One to three sentences describing what this skill accomplishes, followed by key activation triggers. This field is the primary mechanism agents use to decide whether to activate the skill — it is read during discovery before the full body is loaded. Start with a verb. Include the most important "when to use" conditions inline. Max 1024 characters.

write-vignette

9
from pjt222/agent-almanac

Create R package vignettes using R Markdown or Quarto. Covers vignette setup, YAML configuration, code chunk options, building and testing, and CRAN requirements for vignettes. Use when adding a Getting Started tutorial, documenting complex workflows spanning multiple functions, creating domain-specific guides, or when CRAN submission requires user-facing documentation beyond function help pages.