Nothing picked yet. Spin the globe and choose any country you would be glad to end up in — you are not committing to anything. Zoom in on one and its regions and cities appear here.
Shifting departure by a couple of days is routinely the biggest saving on a flight, and being open to it costs nothing.
mid-range hotels, a couple of good meals
Built from everything above. Copy it, paste it into a chatbot, then paste the whole reply into the preview page to see your trip.
We are planning a trip and want two or three different options to compare, not one plan.
We have not narrowed down where to go. Suggest some options, and say why each one fits what we asked for.
Shape of the trip:
- Length: about 10 nights
- Season: Spring
- Dates: flexible by about 3 days either way
- Flying from: not decided
- Travellers: not stated
- Budget: Comfortable
- Pace: Slow — we would rather see less and enjoy it than tick things off
- What we enjoy: Food and markets
HOW TO ANSWER
First, in plain prose, give each option a one-line reason it is different from the
others — not three versions of the same trip. Then sketch the route and roughly how
the nights split between places.
Do not give us a price, an opening time, or an address as if it were current. You
cannot know those. Say so plainly.
Finish with WHAT I DO NOT KNOW — the real gaps. Do not fill a gap with something
plausible. An honest blank is worth more to us than a good guess.
No exclamation marks, and do not call anything a gem or a must-see.
THEN OUTPUT EACH OPTION AS YAML
After the prose, give each option as its own YAML block that I can save straight
into the trips/ folder. Put the filename in a comment on the first line, like:
# trips/option-a-<place>.yml
Use exactly these fields and no others:
name: <short name for the trip>
destination: <where, in a few words>
start: YYYY-MM-DD
end: YYYY-MM-DD
travelers:
- <name>
home_airport: <code>
stale_after_days: 120
stays:
- place: <the base, like "Bergen — near Bryggen">
check_in: YYYY-MM-DD
check_out: YYYY-MM-DD
why: <one line on why this base and not somewhere else>
alternates:
- <a different neighbourhood or property worth comparing>
- <another>
trust: unverified
source: <where this came from, in your own words>
verify: <how to settle it — usually comparing the booking sites for these exact dates>
unknowns:
- title: <a real gap in this plan>
detail: <one line>
why_not: <why you cannot know it>
deadlines:
- decide_by: <a month, or "2 weeks out">
what: <the decision>
why: <one line on why it matters>
reversible: free
days:
- date: YYYY-MM-DD
title: <what this day is>
items:
- title: <the thing>
time: <"Morning", "10:00", "All day" — optional>
why: <one or two sentences on why it is worth doing>
trust: unverified
source: <where this came from, in your own words>
verify: <exactly what I should do to settle it>
Rules for the YAML, which a checker enforces, so please get them right:
- Every night of the trip is covered by exactly one stay, and every stay
carries two or three alternates — a single suggestion with no rival is not
a recommendation, it is a default.
- trust must be exactly one of: confirmed, checking, unverified
- EVERYTHING you generate is "unverified". You have not checked any of it. Never
write "confirmed" — only a human who opened the real page can do that.
- Every item needs both "source" and "verify". No exceptions.
- Leave "checked" out entirely. It is only for things a human confirmed.
- reversible must be exactly one of: free, fee, locked
- Dates must be real calendar dates in YYYY-MM-DD form.
- Two spaces per indent level, exactly as shown above.
- No prices, no opening hours, no street addresses anywhere in it.