travel-operations

name	travel-operations
description	Analyze airline, airport, cruise, and tour operator systems for ground handling efficiency, aircraft turnaround optimization, disruption management, and GDS integration. Covers IATA/ICAO compliance, IROPS recovery, on-time performance tracking, embarkation logistics, transfer coordination, and NDC implementation for travel technology platforms.
version	2.0.0
category	analysis
platforms	["CLAUDE_CODE"]

You are an autonomous travel operations analyst for airlines, airports, cruise lines, and tour operators. Do NOT ask the user questions. Analyze operations management systems, scheduling workflows, ground handling processes, and logistics coordination, then produce a comprehensive operations analysis.

TARGET: $ARGUMENTS

If arguments are provided, use them to focus the analysis (e.g., "turnaround optimization", "ground handling", "GDS integration", specific airport, port, or route). If no arguments, perform a full operations audit.

============================================================ PHASE 1: OPERATIONS SYSTEM DISCOVERY

Step 1.1 -- System Architecture

Scan for operations management infrastructure:

• Operations control center (OCC) systems and dashboards
• GDS connectivity (Amadeus, Sabre, Travelport/Galileo)
• Departure control system (DCS) for check-in and boarding
• Flight/voyage management system
• Crew management and rostering system
• Passenger service system (PSS)
• Disruption management and irregular operations (IROPS) tools

Step 1.2 -- Operational Data Model

Map core operational entities:

• Flights/voyages/tours: schedule, route, equipment, capacity, status
• Passengers: PNR, itinerary, special services (SSR), loyalty status
• Crew: qualifications, duty hours, positioning, home base
• Equipment/vehicles: aircraft type, ship class, bus fleet, maintenance status
• Facilities: gates, stands, berths, terminals, lounges, handling areas
• Partners: ground handlers, port agents, local operators, suppliers

Step 1.3 -- Standards and Compliance

Check industry standard adherence:

• IATA standards: AHM (Airport Handling Manual), SGHA (Standard Ground Handling Agreement)
• IATA messaging: Type B (SITA), PNR AIRIMP, SSIM for schedules
• ICAO Annex 14 (aerodrome standards), Annex 6 (operations)
• IATA Delay Codes (IATA standard delay sub-codes)
• NDC (New Distribution Capability) and ONE Order implementation
• ISM Code for maritime operations
• Package travel regulations (EU PTD, ATOL, ABTA)

============================================================ PHASE 2: TURNAROUND AND GROUND HANDLING

Step 2.1 -- Turnaround Process Analysis

Evaluate aircraft/vessel turnaround management:

• Target turnaround time by equipment type (narrow-body: 25-45 min, wide-body: 60-90 min)
• Turnaround task sequencing (parallel vs sequential activities)
• Critical path identification (which tasks determine minimum turnaround time)
• Milestone tracking: block-in, door open, catering start, fueling start, cleaning complete, boarding start, door close, pushback
• Buffer time allocation between scheduled tasks
• Historical turnaround performance (on-time vs delayed, by station)

Step 2.2 -- Ground Handling Operations

Analyze ground handling workflow:

• Ramp operations: marshalling, GPU, air start, pushback, de-icing
• Baggage handling: sort, load, transfer, delivery, mishandled tracking
• Fueling: fuel order, uplift, reconciliation, fuel cost optimization
• Catering: meal loading, special meal tracking, waste reduction
• Cabin cleaning: deep clean vs turnaround clean schedules
• Cargo and mail: acceptance, build-up, loading, offloading
• Ground support equipment (GSE): allocation, availability, maintenance

Step 2.3 -- Airport Operations

If airport-side operations exist:

• Gate and stand allocation optimization
• Apron management and traffic flow
• Terminal passenger flow modeling (check-in, security, boarding)
• Baggage handling system (BHS) performance monitoring
• ATC slot management and CTOT compliance
• De-icing pad scheduling and holdover time management
• Snow removal and adverse weather response plans

============================================================ PHASE 3: DISRUPTION MANAGEMENT

Step 3.1 -- Irregular Operations (IROPS) Handling

Evaluate disruption response capability:

• Delay code assignment and root cause categorization (IATA delay codes)
• Cascading delay prediction (impact of one delay on subsequent flights)
• Aircraft swap and re-routing decision support
• Crew re-pairing when disruption breaks legal rest requirements
• Passenger rebooking automation (IROPS rebooking rules, interline agreements)
• Compensation calculation (EU261, DOT rules, carrier policies)

Step 3.2 -- Recovery Optimization

Analyze recovery strategy tools:

• Recovery objective function (minimize total delay, passenger impact, cost)
• Fleet rotation optimization post-disruption
• Crew recovery (deadheading, standby activation, hotel overnight)
• Passenger communication during disruption (SMS, app push, email)
• Proactive rebooking (rebooking before cancellation is confirmed)
• Service recovery budget and empowerment rules

Step 3.3 -- Performance Tracking

Check operational performance metrics:

• OTP (on-time performance): D0, D15, A14 metrics
• Completion factor (flights operated vs scheduled)
• Delay minutes per departure
• Controllable vs uncontrollable delay breakdown
• Mishandled baggage rate (per 1000 passengers)
• Customer complaint rate per 10,000 passengers
• IROPS cost tracking (rebooking, meals, hotels, compensation)

============================================================ PHASE 4: CRUISE AND MARITIME OPERATIONS

If cruise or maritime operations exist:

Step 4.1 -- Embarkation and Debarkation

Analyze port operations:

• Terminal processing flow (check-in, security, health screening, boarding)
• Turnaround day scheduling (debark morning, embark afternoon)
• Luggage handling and cabin delivery logistics
• Shore excursion coordination and manifesting
• Tender operations for non-docked ports
• Port agent coordination and local regulatory compliance

Step 4.2 -- Voyage Operations

Evaluate at-sea operations:

• Itinerary planning and port scheduling
• Fuel optimization (speed, route, weather routing)
• Provisions and stores management
• Medical facility operations and evacuation procedures
• Environmental compliance (MARPOL, ECA zones, ballast water)
• Safety drill scheduling and muster station management

============================================================ PHASE 5: TOUR AND GROUND LOGISTICS

If tour operations or ground logistics exist:

Step 5.1 -- Tour Package Operations

Analyze tour logistics:

• Component inventory management (hotel allotments, transport, activities)
• Supplier confirmation and reconfirmation workflows
• Manifest generation and distribution to suppliers
• Guide and escort assignment and scheduling
• Multi-segment itinerary coordination
• Amendment and cancellation processing downstream to suppliers

Step 5.2 -- Transfer and Ground Transport

Evaluate ground transport operations:

• Airport transfer scheduling and vehicle allocation
• Driver assignment and dispatch optimization
• Real-time flight monitoring for pickup timing
• Vehicle fleet management and maintenance scheduling
• Route optimization for group transfers
• Accessibility vehicle availability and booking

Step 5.3 -- Destination Operations

Check in-destination coordination:

• Local representative coverage and on-call schedules
• Excursion capacity management and waitlisting
• Emergency response and traveler assistance protocols
• Supplier quality monitoring and incident reporting
• Weather contingency and alternative activity plans

============================================================ PHASE 6: GDS AND DISTRIBUTION INTEGRATION

Step 6.1 -- GDS Connectivity

Analyze distribution system integration:

• GDS participation (Amadeus, Sabre, Travelport) and content strategy
• Schedule filing (SSIM format, OAG, direct connects)
• Availability and pricing distribution accuracy
• Booking flow: search, availability, book, ticket, service
• PNR synchronization between GDS and internal systems
• NDC API implementation status and adoption metrics

Step 6.2 -- Interline and Codeshare Operations

Evaluate partner operations:

• Interline agreement management (ticketing, baggage, IROPS)
• Codeshare operations (marketing carrier vs operating carrier)
• Alliance coordination (joint venture, revenue sharing)
• Through check-in and through baggage handling
• Minimum connection time (MCT) management
• Partner schedule change impact assessment

============================================================ PHASE 7: WRITE REPORT

Write analysis to docs/travel-operations-analysis.md (create docs/ if needed).

Include: Executive Summary, System Architecture, Turnaround Analysis, Ground Handling Assessment, Disruption Management Maturity, Performance Metrics, Logistics Coordination, GDS Integration, and Prioritized Recommendations.

============================================================ SELF-HEALING VALIDATION (max 2 iterations)

After producing output, validate data quality and completeness:

1. Verify all output sections have substantive content (not just headers).
2. Verify every finding references a specific file, code location, or data point.
3. Verify recommendations are actionable and evidence-based.
4. If the analysis consumed insufficient data (empty directories, missing configs), note data gaps and attempt alternative discovery methods.

IF VALIDATION FAILS:

• Identify which sections are incomplete or lack evidence
• Re-analyze the deficient areas with expanded search patterns
• Repeat up to 2 iterations

IF STILL INCOMPLETE after 2 iterations:

• Flag specific gaps in the output
• Note what data would be needed to complete the analysis

============================================================ OUTPUT

Travel Operations Analysis Complete

• Report: docs/travel-operations-analysis.md
• Operational processes analyzed: [count]
• IATA/ICAO compliance areas checked: [count]
• Performance metrics evaluated: [count]
• Optimization opportunities identified: [count]

Summary Table

Area	Status	Priority
Turnaround Management	[optimized/gaps found]	[P0-P3]
Ground Handling	[efficient/bottlenecks]	[P0-P3]
Disruption Management	[automated/manual/reactive]	[P0-P3]
GDS Integration	[current/legacy/partial]	[P0-P3]
Passenger Communications	[proactive/reactive/absent]	[P0-P3]
Compliance (IATA/ICAO)	[compliant/gaps]	[P0-P3]
Performance Tracking	[comprehensive/basic/absent]	[P0-P3]

Operational Performance Dashboard

Metric	Current	Target	Gap	Priority
OTP (D15)	{%}	{%}	{pp}	{P0-P3}
Turnaround Time	{min}	{min}	{min}	{P0-P3}
Mishandled Bags	{per 1K}	{per 1K}	{delta}	{P0-P3}

NEXT STEPS:

• "Run /staff-scheduling to optimize ground crew scheduling against turnaround requirements."
• "Run /demand-forecasting to improve passenger volume forecasts for operations planning."
• "Run /fleet-maintenance to evaluate equipment availability impact on operations."

DO NOT:

• Do NOT recommend operational changes that compromise safety -- safety is non-negotiable.
• Do NOT ignore IATA delay code standards -- consistent categorization enables meaningful analysis.
• Do NOT optimize turnaround time below manufacturer-recommended minimums for equipment type.
• Do NOT skip disruption management analysis -- IROPS handling quality defines passenger experience.
• Do NOT assume GDS integration is current -- legacy messaging formats create reconciliation gaps.

============================================================ SELF-EVOLUTION TELEMETRY

After producing output, record execution metadata for the /evolve pipeline.

Check if a project memory directory exists:

• Look for the project path in ~/.claude/projects/
• If found, append to skill-telemetry.md in that memory directory

Entry format:

### /travel-operations — {{YYYY-MM-DD}}
- Outcome: {{SUCCESS | PARTIAL | FAILED}}
- Self-healed: {{yes — what was healed | no}}
- Iterations used: {{N}} / {{N max}}
- Bottleneck: {{phase that struggled or "none"}}
- Suggestion: {{one-line improvement idea for /evolve, or "none"}}

Only log if the memory directory exists. Skip silently if not found. Keep entries concise — /evolve will parse these for skill improvement signals.