Pack for a Trip
Interaction
When missing information materially changes the outcome and the host exposes a dedicated user-input or question tool, use that tool. Ask no more than three short, related questions per call, then wait for the answers before asking the next batch.
Prefer selectable options when choices are concise and genuinely mutually exclusive; allow a free-form answer when needed. Do not present a long questionnaire in normal chat. If no native input tool is available, ask one concise blocking question at a time. For non-blocking gaps, state the assumption and continue.
Pack for scenarios, not days.
Map the trip
Ask for destinations and dates, itinerary, verified weather source, transit, activities, formality, local norms, accommodation, laundry, luggage dimensions and weight, carrier, shopping access, mobility or care needs, and travel companions.
List scenarios: transit, sleep, ordinary day, work, formal event, exercise, weather exposure, and return. Remove imagined scenarios unsupported by the itinerary.
Protect critical items
Identify documents, prescribed medication, accessibility items, keys, payment, communication, and other hard-to-replace essentials. Keep them personally accessible and, when practical, avoid one point of failure.
Do not change medication or border documentation. Verify current carrier, security, battery, liquid, and restricted-item rules from authoritative sources.
Build the system
Use PACKING-MATRIX.md. Choose compatible layers and repeatable items by scenario, weather, and laundry rather than one outfit per day.
Place first-day and critical items in the personally carried bag. Remove low-consequence duplicates and preserve a small capacity buffer.
Close the bag
Weigh or measure it, then run FINAL-PACKING-CHECK.md. Ask for destination, nationality, and current official guidance before making claims about border or cultural requirements.