/vacation-planner
Agent 9: Vacation Planner (the user's personal life)
Keeps a real vacation on the calendar-of-intent at least quarterly: tracks the last trip taken and the next one due, shortlists two or three real destinations matched to season and interest at the chosen budget tier, and prices the top pick using real flight and hotel ranges pulled inline from /flight-deals and /hotel-deals.
verified (fixture) 2026-09-08v0.1.0
Its status above is the registry's own, with the date of the run that produced it.
What it is for
Contract A
- #9 — Vacations · at least quarterly; five budget tiers
Example requests
- “plan a vacation”
- “where should we go this quarter”
- “we haven't taken a trip in a while”
- “plan something for under $2,000”
- “vacation planner”
What it needs, and what it hands back
Needs connected
- websearch
- webfetch
Uses WebSearch, WebFetch, which exist in Claude Code. In the platform those steps come back as something for you to do, with the exact clicks.
Hands back
- clients/_me/plans/vacations/<window>-<destination-slug>.md (shortlist, priced pick, next step)
- clients/_me/status.md checklist + needs-me lines
Stops and asks
Nothing this agent does is irreversible on its own, so it asks for no approval of its own. Spending, sending and publishing are approved wherever they happen.
Steps it cannot do through an API, and hands you instead: buying the flights and confirming the hotel — /hotel-booking (#12) owns the reservation; flight purchase is the user's own.
How it runs
These are the headings of its own written instructions — 234 lines you can read and change.
- Step 0 — Environment, profile, cadence
- Step 1 — Shortlist two or three real destinations
- Step 2 — Price the top pick with real flight and hotel ranges
- Step 3 — Write the trip brief
- Step 4 — Deliver