Travel Command Center
Centralize your entire trip in one workspace — itinerary, bookings, packing list, and restaurant picks that all reference each other.
Your trip details are scattered across 12 confirmation emails, a Google Doc itinerary, and random screenshots of restaurant recommendations. This playbook centralizes your entire trip in one workspace — itinerary, bookings, packing list, and restaurant picks that all cross-reference each other.
Who it's for: frequent business travelers managing complex multi-city itineraries, families planning vacations with many moving parts and group preferences, digital nomads coordinating accommodations and workspaces across destinations, executive assistants organizing travel for multiple executives, group trip organizers coordinating logistics for friends or colleagues
Example
"Organize my 10-day Japan trip into one command center" → Travel pipeline: master itinerary with day-by-day schedule linked to booking confirmations, accommodation details with check-in times and addresses, restaurant recommendations mapped to nearby daily activities, weather-aware packing list with destination-specific items, and transportation overview with train passes and transfer instructions
New here? 3-minute setup guide → | Already set up? Copy the template below.
# Travel Command Center
## Role
You help me plan trips with everything in one connected workspace. You create linked documents for itinerary, bookings, dining, packing, and logistics so nothing falls through the cracks.
## Directory Structure
- `trip-master.md` — Overview: dates, destination, bookings, documents needed
- `itinerary.md` — Day-by-day plan with times, transit, and backup options
- `packing.md` — Activity-specific packing list with buy-before-trip flags
- `restaurants.md` — Restaurant picks: cuisine, price, must-try dish, best day
- `bookings/` — Confirmation details for flights, hotels, activities
## Rules
1. Itinerary must include realistic transit times between locations
2. Always include bad-weather backup options for outdoor activities
3. Packing list must reference planned activities specifically
4. Restaurant list should note which itinerary day each fits best
5. Flag any booking conflicts or scheduling impossibilities
## Commands
- "/plan [destination] [dates]" — Create master trip document
- "/itinerary [preferences]" — Build daily itinerary balancing preferences
- "/pack" — Generate activity-specific packing list from itinerary
- "/eat" — Create restaurant list matched to itinerary days
- "/checklist" — Pre-trip checklist: documents, bookings, purchases neededWhat This Does
Puts your entire trip in one connected workspace. Flights, hotels, daily itinerary, restaurant list, and packing list all reference each other — so your packing list matches your planned activities and your restaurant picks fit your daily schedule.
Inspired by Marco Kotrotsos's 20 Non-Coding Uses for Claude's Code Mode.
Prerequisites
- Claude Code installed
- A destination and travel dates
- Any existing booking confirmations
Step-by-Step Setup
- Create a folder for your trip
- Save the CLAUDE.md template
- Start with the master plan, then build daily itinerary
- Generate packing and restaurant lists from the itinerary
- Add booking confirmations as you make them
Example Usage
"Planning a 7-day trip to Japan from March 10-17. Create the master doc"
"Build a daily itinerary balancing temples, food, and relaxation"
"Generate a packing list specific to the activities planned"
"Create a restaurant list — which day does each fit best?"
"What do I need to buy or book before the trip?"
Tips
- Start with the master document and itinerary before details
- Transit times are where most trip plans fail — be realistic
- Bad-weather backups save ruined days
- Update booking files as confirmations come in