plan-hiking-tour
정보
이 스킬은 개발자가 SAC/UIAA 난이도 기준으로 등산로를 선정하고, 뮌터 공식을 사용해 소요 시간을 산출하며, 고도와 안전성을 평가하는 하이킹 투어 플래너를 구축할 수 있도록 돕습니다. 일일 하이킹, 여러 날에 걸친 산장 간 투어, 그룹 체력 수준을 고려한 알파인 루트 계획을 지원합니다. 앱에서 현실적인 하이킹 일정 생성, 소요 시간 계산, 또는 숙박 트레킹 로지스틱 관리가 필요할 때 사용하세요.
빠른 설치
Claude Code
추천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-tourClaude Code에서 이 명령을 복사하여 붙여넣어 스킬을 설치하세요
문서
Wandertour planen
Planen a hiking tour with trail selection, time estimation, elevation analysis, and safety assessment for groups of varying fitness levels.
Wann verwenden
- 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
Eingaben
- Erforderlich: Region or area for the hike
- Erforderlich: Group profile (number of people, fitness level, experience)
- Erforderlich: 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
Vorgehensweise
Schritt 1: Definieren Requirements
Establish der 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
Dokumentieren the group's weakest-link fitness level, as this determines the maximum difficulty.
Erwartet: A clear requirements profile with group level, time budget, elevation tolerance, and any must-include or must-avoid constraints.
Bei Fehler: 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).
Schritt 2: Auswaehlen Trail Candidates
Research and shortlist trails matching the requirements.
Sources for trail data:
- Hiking guidebooks and regional websites
- OpenStreetAbbilden (trails tagged with
sac_scale) - National/regional trail databases (e.g., SchweizMobil, Alpenverein)
- WebSuchen for "[region] hiking trails [difficulty]"
Fuer jede 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.
Erwartet: A shortlist of trail candidates with complete data sheets, all innerhalb the group's capability range.
Bei Fehler: If no trails match all constraints, relax the least important constraint first (typischerweise distance vor difficulty). If trail data is incomplete, note the gaps and plan to verify on-site or contact local tourism offices.
Schritt 3: Berechnen Times Using Munter Formula
Schaetzen 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
Erwartet: Time estimates fuer jede trail candidate, einschliesslich break time. Estimates sollte conservative (better to arrive early than to hike in darkness).
Bei Fehler: 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 basierend auf actual performance.
Schritt 4: Bewerten Safety
Bewerten 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
Erwartet: A completed safety assessment with all hazards rated and mitigations documented. An overall GREEN/YELLOW/RED rating for the go/no-go decision.
Bei Fehler: 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.
Schritt 5: Planen Logistics
Organisieren 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:
- Book huts well in advance (popular huts fill months ahead)
- Planen resupply points for food and water
- Identifizieren bail-out points fuer jede day (where to exit if someone is injured or weather turns)
- Teilen the itinerary with someone not on the hike
Erwartet: All logistics confirmed or flagged as pending. Hut reservations made. Transport to/from trailhead arranged. Emergency plan documented.
Bei Fehler: 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.
Schritt 6: Generieren 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
Erwartet: A complete hiking plan that kann shared with all participants and left with an emergency contact. The plan sollte actionable ohne additional research.
Bei Fehler: If the plan has gaps that cannot be filled vor departure, document them clearly and assign someone to resolve each item. Critical safety gaps (no escape route identified, no weather check plan) muss resolved vor departure.
Validierung
- 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 fuer jede segment
- Escape routes are mapped fuer jede 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)
Haeufige Stolperfallen
- 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 (typischerweise early nachnoon for alpine routes) to avoid descending in darkness or nachnoon thunderstorms.
- Skipping the backup route: Weather and conditions change. Always have an easier alternative prepared.
- Overloaded first day: Starten with a shorter, easier day to assess group pace and acclimatize, besonders 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 (besonders in the Alps) require reservations weeks or months in advance. Never assume walk-in availability in high season.
Verwandte Skills
check-hiking-gear— generate an optimized gear checklist for the planned hikeassess-trail-conditions— evaluate current conditions on the selected trailplan-tour-route— broader tour planning for non-hiking segmentscreate-spatial-visualization— visualize the hiking route and elevation profilegenerate-tour-report— compile the hiking plan into a formatted report
GitHub 저장소
연관 스킬
executing-plans
디자인executing-plans 스킬은 검토 체크포인트가 포함된 통제된 배치로 실행할 완전한 구현 계획이 있을 때 사용합니다. 이 스킬은 계획을 불러와 비판적으로 검토한 후, 소규모 배치(기본값 3개 작업)로 작업을 실행하면서 각 배치 사이에 진행 상황을 아키텍트 검토를 위해 보고합니다. 이를 통해 내재된 품질 관리 체크포인트를 갖춘 체계적인 구현이 보장됩니다.
requesting-code-review
디자인이 스킬은 코드 변경 사항을 요구 사항에 따라 분석하기 위해 코드 리뷰어 하위 에이전트를 호출합니다. 작업 완료 후, 주요 기능 구현 후, 또는 메인 브랜치에 병합하기 전에 사용해야 합니다. 이 리뷰는 현재 구현체와 원래 계획을 비교하여 문제를 조기에 발견하는 데 도움이 됩니다.
connect-mcp-server
디자인이 스킬은 개발자들이 HTTP, stdio 또는 SSE 전송 방식을 통해 MCP 서버를 Claude Code에 연결하는 포괄적인 가이드를 제공합니다. GitHub, Notion 및 사용자 정의 API와 같은 외부 서비스를 통합하기 위한 설치, 구성, 인증 및 보안을 다룹니다. MCP 통합 설정, 외부 도구 구성 또는 Claude의 모델 컨텍스트 프로토콜 작업 시 활용하세요.
web-cli-teleport
디자인이 스킬은 작업 분석을 기반으로 개발자가 Claude Code 웹 인터페이스와 CLI 인터페이스 중 선택할 수 있도록 돕고, 두 환경 간 원활한 세션 텔레포트를 가능하게 합니다. 웹, CLI 또는 모바일 환경 전환 시 세션 상태와 컨텍스트를 관리하여 워크플로를 최적화합니다. 다양한 단계에서 서로 다른 도구가 필요한 복잡한 프로젝트에 사용하세요.
