Travel Advisor — Peak-End Experience Design

SKILL.md

---
name: travel-experience-peak-end-design
description: "Activate when: designing an itinerary you want remembered and referred; planning honeymoon/milestone/luxury trips; 'how do I get repeat clients and referrals?'; setting surprise-and-delight touches. Do NOT activate when: pure transactional booking with no relationship goal."
---

# Travel Advisor — Peak-End Experience Design

> **Industry front door for peak-end-rule.** Adds domain triggers, example, packs only. Parent Process unchanged.

**Activate when:** designing an itinerary you want remembered and referred; planning honeymoon/milestone/luxury trips; "how do I get repeat clients and referrals?"; setting surprise-and-delight touches.
**Do NOT activate when:** pure transactional booking with no relationship goal.

## Why this variant
The parent peak-end-rule says memory is dominated by the emotional **peak** and the **end**, not the average. Referrals and repeat bookings — a travel advisor's cheapest growth — are bought by engineering one clear peak and a strong finish, not by spreading budget evenly.

## Domain inputs → parent's Process
- Identify the intended **peak** moment; over-invest there (upgrade, private guide, timed reservation).
- Engineer the **end**: last-day/departure touch (lounge, transfer, welcome-home note) so the trip closes high.
- De-risk the **low** (arrival friction, jet-lag day) since a bad start/end disproportionately scars memory.

## Worked example
10-day Italy trip, flat mid-range spend throughout.
→ Redirect budget: one unforgettable peak (private after-hours gallery) + a strong end (final-night terrace dinner + airport fast-track). Same total cost, materially higher remembered value → referral.

## Packs
- **Solo:** define the one peak + the end touch on every leisure itinerary.
- **Luxury:** signature surprise moment as a repeatable brand asset.

## Red flags
- Budget spread evenly with no engineered peak.
- Trip ends on a logistics slog (long transfer, no send-off).
- Arrival-day friction left unmanaged.

## Verification
- [ ] One deliberate peak identified and funded
- [ ] End touch designed
- [ ] Arrival/low-point friction reduced
- [ ] Post-trip referral ask timed to the high

---
Part of **deciqAI Knowledge Skills**. Core method: peak-end-rule.

---

*Part of **deciqAI Knowledge Skills** — 189 open-source thinking skills that make rigor executable for AI agents. The same skills power every deciqAI agent, which runs them autonomously to operate your company. **See it run → https://www.deciqai.com/c/travel-experience-peak-end-design** · ⭐ Star the repo → https://github.com/deciqAI/knowledge-skills · Contributions welcome.*