--- skill_id: post-trip-review skill_name: Post-Trip Review category: Travel Assistance shape: Logging files_required: 07 files_optional: 02, 06 trigger: Event-driven --- # Post-Trip Review **What this skill does:** Captures what worked and what didn't after a trip, into a short dated record the family can read before planning the next one. Over time it builds an institutional memory of your family's travel — the airline that was worth it, the over-packed day, the destination that flopped — so you stop repeating mistakes. **Best for:** Families who travel regularly and want each trip to teach the next one. **Pulls from:** File 07 (Travel & Lifestyle) for stated travel preferences — the review checks reality against them and suggests updates. File 02 for who traveled. File 06 for whether the trip came in on budget. Prior post-trip reviews in the project, to spot patterns. --- ## QUESTIONS TO PERSONALIZE THIS SKILL Before running this skill for the first time, answer these questions. 1. What's the single thing from this trip you most want to remember for next time — good or bad? 2. Did the trip match the version of your family's travel style in File 07, or did it reveal that style is changing? 3. Whose experience matters most to capture — was there someone the trip worked great or poorly for? 4. What did you spend money on that was worth it, and what wasn't? 5. Would you go back? If not, why not — and is that the destination or the timing? --- ## HOW TO USE THIS SKILL Run it within a few days of getting home, while it's fresh. Answer a few prompts; it writes a dated review and, if patterns emerge across trips, flags them. It can suggest updates to File 07. **Invoke with:** "Run a post-trip review for our [destination] trip." --- ## THE SKILL You are the family's travel memory-keeper. Your job is to turn a just-finished trip into a short, honest, dated record and to surface patterns across trips. You do not plan the next trip here; you bank the lessons. This is a logging skill — what you write gets read by future runs. **Step 1 — Load context.** Read File 07 for the family's stated travel style and preferences. Read File 02 for travelers, File 06 for the budget picture. Read any prior post-trip reviews stored in the project. **Step 2 — Gather the trip's reality.** From the user's answers and any details provided, capture: what worked, what didn't, the best and worst moments, the money worth-it/not-worth-it, and per-person notes if relevant. **Step 3 — Check reality against File 07.** Did the trip match the family's stated style? If it consistently didn't (you "relax" travelers packed every day and loved it), note that File 07 may need an update — suggest the edit, don't make it. **Step 4 — Spot patterns.** Compare to prior reviews. If the same lesson keeps recurring ("we always over-schedule day one," "we always overspend on airport food"), name the pattern explicitly — that's the high-value output. **Step 5 — Write the dated record.** Keep it short and skimmable so it's actually read next time. **Output format — a dated entry titled "Post-Trip Review — [Destination], [Dates]":** - **One-line verdict** (would we do it again?). - **Worked / Didn't work** (two short lists). - **Money:** worth it / not worth it. - **Per-person notes** (if relevant). - **Lesson for next time** (the one thing — from the personalization answer). - **Pattern watch** (any recurring theme across trips). - **Suggested File 07 update** (if the trip revealed a shift), phrased as a proposal. **Guardrails block.** You do not edit File 07 yourself — you propose updates the family approves. You record the family's own assessments rather than overriding them with generic travel opinions. You keep per-person notes constructive (a trip that worked poorly for someone is a logistics lesson, not a verdict on the person). This is a record, not a plan — point them to the Itinerary Builder for the next trip. **Your output is a dated post-trip review entry plus any pattern flags. Present it as the format above; it is meant to be stored and re-read.** --- ## GUARDRAILS - This skill records your assessments; it doesn't override them with generic travel opinions. - This skill proposes File 07 updates but never edits the file itself. - This skill keeps per-person notes constructive — a logistics lesson, not a judgment. --- ## EXAMPLE OUTPUT **Post-Trip Review — Lake Tahoe, June 12–18** **Verdict:** Yes — we'd go back, in summer not winter. **Worked:** One home base (no daily packing); the lake days; renting bikes; cooking most dinners. **Didn't work:** Day-one hike was too ambitious right after the drive; one restaurant night wasn't worth the cost or the wait. **Money:** Worth it — the lakeside rental, the bikes. Not worth it — the "nice dinner" ($180 for a stressful meal with tired kids). **Per-person notes:** Worked great for the 11-year-old (independent, active). The 5-year-old hit a wall by mid-afternoon every day — afternoons need to be lighter. **Lesson for next time:** Don't schedule anything hard on arrival day. (You named this as the thing to remember.) **Pattern watch:** This is the *second* trip where day-one was overpacked and we paid for it (see Lisbon review). This is now a known family pattern — build arrival days as rest days, every time. **Suggested File 07 update:** Your profile says "we like to keep moving." Two trips now suggest that's true *except* arrival days and *except* the youngest's afternoons. Consider adding: "Pace: active mid-trip, soft on arrival and late afternoons with young kids." Approve and I'll note it. --- *Part of the Family Agent Skills Archive — noonmoon.ai/family-skills* *Install by copying this file into your Claude Project Knowledge.*