Use when planning a personal or work trip - lodging, transport, daily plan, packing
Scanned 5/27/2026
Install via CLI
openskills install redhuntlabs/wizard---
name: planning-a-trip
description: Use when planning a personal or work trip - lodging, transport, daily plan, packing
kind: workflow
audience: anyone
ai-tools: any
complexity: guided
time: 20-40 min
version: 1.0.0
source: bundled
---
# Planning a Trip
## What this does
Walks you from a vague trip idea to a complete plan: dates, route, lodging, daily structure, and a packing list — without overplanning the things that don't matter.
## When to use
- Planning a personal trip (vacation, family visit, weekend away)
- Planning a work trip (conference, customer visit, offsite)
- Planning the logistics of a trip you've already committed to
## What you bring (Inputs)
- Destination(s) and rough dates
- Trip purpose (rest / explore / event / mixed)
- Constraints (budget, dietary, accessibility, kids, pets)
- Anchor commitments (flights you've booked, events you must attend)
## What you get (Output)
A trip plan: dates + transport + lodging + day-by-day skeleton + packing checklist + a small "open questions" list.
## How it works (Steps)
This is a guided workflow.
## Stages
### Stage 1: Anchor
Lock the immovable: dates, must-attend events, return-by deadline.
### Stage 2: Route and transport
Pick lodging-to-event transport (walk / transit / rental car / rideshare). Book the longest, hardest piece first (long flights, train passes).
### Stage 3: Lodging
Pick lodging by criteria in this order: proximity to anchor events, sleep quality (reviews mention noise / bed), then price. Book.
### Stage 4: Day-by-day skeleton
For each day, write 1-2 anchors (event, meal, sight) and leave the rest open. Overplanning produces brittle trips.
### Stage 5: Packing checklist
Generate a checklist by category: docs, electronics, clothes (per weather), toiletries, meds, comfort items.
### Stage 6: Open questions
List what you couldn't decide yet (e.g., "decide on dinner spots day-of"). Naming them prevents anxiety.
## Checkpoints
- **After Stage 1**: dates and anchors locked
- **After Stage 2**: long-haul transport booked
- **After Stage 3**: lodging confirmed
- **After Stage 4**: each day has 1-2 anchors and free time
- **After Stage 5**: checklist exists
- **After Stage 6**: open questions captured
## Loop-back conditions
Return to Stage 2 if lodging quality forces a transport change.
## Quality bar
- Every booked thing has a confirmation number captured
- Daily plan has 1-2 anchors per day, not 5
- Packing list is checked twice: once when packing, once at the door
- Open questions are written down (not in your head)
## Variations
- **Conference trip**: anchors are sessions; build day-by-day from the schedule
- **Family trip**: add a "kid backup plan" line per day (snack/nap/screen)
- **Solo rest trip**: skip Stage 4's anchors entirely
## Example
**Input**: 4 days in Lisbon, mostly rest, one wedding on day 2, travel light.
**Output**:
> Dates: Apr 18-21. Anchor: wedding Sat 4pm.
> Transport: TAP from JFK Apr 17 night arrival; Uber from airport.
> Lodging: 4 nights at <hotel> (5-min walk to wedding venue).
> Day-by-day:
> - Apr 18: arrive, lunch + nap, walking tour (4-7pm)
> - Apr 19: wedding (4pm-late)
> - Apr 20: late breakfast, beach day
> - Apr 21: depart 11am
> Packing: <list>.
> Open: dinner Apr 18, beach choice Apr 20.
No comments yet. Be the first to comment!