The classic bucket list is twenty-three lines on a page in a journal you opened twice. Hike the Camino. Learn to make pasta from scratch. See the northern lights. Take a writing class. Each line was a real intention when you wrote it. None of them have moved an inch.
The problem isn't ambition. It's that bucket lists usually live as bare titles, with no path from "this would be amazing" to "I booked the flight." The list itself becomes a kind of museum — admired occasionally, never visited.
A vault that gives each item its own page, with the planning material and the small first steps written out, turns a list into a working set of intentions. The agent does the searching and the prompting; you do the actual living. (For the underlying habit of catching the intention the moment it shows up, The Capture Habit: Remembering the Things That Actually Matter is the companion.)
One page per item, not one bullet on a list
In a markdown vault like Docapybara, each bucket-list item gets its own page, named after the thing. Pages nest with no depth limit, so a single Bucket list parent page can have a child page for every item, and each item can grow its own sub-pages as the planning gets real.
The page starts almost empty. Just the title, a paragraph on why this matters to you, and the next concrete action. Hike the Camino: I want a long walk that's structured but solitary, and I want to do it before my fortieth birthday. Next action: read three first-person accounts of doing it solo.
That last sentence is what separates a list that moves from a list that doesn't. Every item has a next action — something small, specific, and doable in under an hour. If the next action would take a week, it's not the next action; it's the goal. The next action is the read-three-accounts step that gets you there.
A capture habit that doesn't filter too early
Most things that should be on a bucket list arrive at moments when you can't write them down properly — mid-walk, mid-conversation, mid-plane. The capture has to be friction-free or the moment passes.
Voice is the right tool here. Tap record, talk for ten seconds. "I want to learn to ferment vegetables. The kimchi at that restaurant tonight reminded me. Add to bucket list." That's enough — the transcription lands on a page, the agent can file it later.
The point of capturing immediately is that you're catching the feeling alongside the item. "I want to learn to ferment vegetables — the kimchi at that restaurant tonight reminded me" is a much richer record than just "learn fermenting." Six months from now when you're deciding what to actually start, the feeling helps you remember why you cared.
For items that show up while reading or scrolling, the same approach works in text — drop the link or the screenshot on a quick capture page, and ask the agent later: "Look at the things I've captured this month and add anything that feels like a bucket-list intention to the bucket list."
A list that sorts itself by what you can actually do next
Bucket lists usually fail because they mix the trivially-doable with the years-long. Try the new ramen place sits next to Live in Japan for a year, and your brain bounces between them and does neither.
A Status column on the bucket list makes the difference visible. An inline :::database::: directive lets a small spreadsheet live on the Bucket list page, with columns for item, why I want this, status (someday / planning / in progress / done), next action, target window, and a date added.
The agent maintains it. "Show me everything in 'planning' status, sorted by how long it's been there." You get the list of intentions that have started moving and might be due for the next step. "List the someday items I've added in the last six months — I want to see what's been on my mind lately." The list returns with capture dates.
Six column types are available — text, numbers, dates, checkboxes, single-select, multi-select — so you can mix categorical fields like cost level and time commitment without forcing everything into prose.
Planning that can grow when an item gets real
When an item moves from someday to planning, the page can grow. For a trip — say Hike the Camino — you'd add child pages for Logistics (flights, route options, gear), Reading (the books and accounts you've gathered), and Training (a small build-up walking plan if you need it).
Drop the relevant PDFs on the right child page. Travel-blog PDFs, a route map, a gear guide — all converted to markdown automatically so the agent can read them. "Read the three Camino accounts I've saved and tell me what gear they all agreed was essential." You get a list grounded in the actual sources, not a generic packing list.
For a learning goal — say Learn to make pasta from scratch — the planning is different. A Resources child page with the YouTube channels, the recipe PDFs, the book recommendations. A Practice log child page where you note what you tried and how it went. (More on the learn-a-skill version of this in AI Notes for Learning a New Skill.)
The shape adapts to the item. The vault doesn't force you to plan a trip and a hobby the same way.
Research without leaving the page
Bucket-list research is the part where most people lose momentum. You start looking up the cost of a Camino tour, get distracted by an article on Spain, end up reading about something else entirely, and don't come back to the planning for a month.
Keeping the research inside the page helps. The agent's web_search tool can pull current information without sending you to a tab where you'll get lost. "Find what current Camino walkers recommend as the best month to start the Camino Frances." Comes back with sources you can read later. "Search for fermenting workshops near me in the next three months." Same deal — results land in the page as a record of what you found.
For long-running research, the search results compound. Six months in, the Hike the Camino page has gathered enough material that the planning starts to feel concrete. The agent can summarize: "Look at everything I've gathered about the Camino over the last few months. What's the most consistent advice and what are the open questions I still need to resolve?" For trip-shaped items specifically, Documenting Travel Itineraries and Trip Research Without the Tab Sprawl covers it from the trip-planning side.
A "what's in motion" view that keeps things honest
The honest question for a bucket list is: what's actually moving? Not what's on the list. What has progressed in the last month.
A What's moving page can hold the answer, refreshed monthly. Ask the agent: "Look at the bucket list. For each item in 'planning' or 'in progress' status, summarize what's happened in the last month — any new research, any next actions completed, any decisions made." You get a clean status report on your own intentions.
Two things tend to happen when you actually look. Items that aren't moving and that you don't feel guilty about not moving — those can come off the list. They served their purpose as a momentary intention; they don't need to live in your head as unfinished business. Items that aren't moving but that you do feel guilty about — those need a smaller next action. The next action you wrote was probably too big.
For the items that did move, the same view is genuinely satisfying. Reading a clean summary of "this month you booked the flight, finalized the route, and ordered the boots" is a small but real reward.
When something gets done — a real record
Items that get done deserve more than a checkbox. The completed bucket-list items are also some of the most memorable experiences in your life, and the page is a good place for them to live.
Voice works for the after-the-fact writeup. "Just got back from the Camino. Twenty-eight days. The third day my feet were destroyed and I almost quit; I'm glad I didn't. The thing I'll remember most is the Dutch couple I met outside Burgos who walked with me for four days and then I never saw them again. Worth every bit of effort." Ten minutes of talking, transcribed, on the page.
The agent can pull patterns over time. "Look at the bucket-list items I've completed. What's the common thread in what I found most rewarding?" The answer might surprise you — and might shape what stays on the list going forward.
Photos and audio from the experience can land on the same page. PDFs of the route map, the receipts, the journal you kept along the way — all searchable, all in one place.
A starter shape that works on day one
If you're starting today, here's what we'd suggest:
- Bucket list — one parent page, with the inline database.
- Quick captures — one page where new intentions land before you sort them.
- For the three or four items most active in your mind right now — one child page each, with the why, the next action, and any planning that's already started.
Three or four active items is plenty. The list of someday intentions can grow as much as you want; the working set should be small enough that you actually look at it.
The point isn't to optimize a bucket list. It's that the things you've said you want to do start moving — quietly, in small steps, in a place where the next step is always visible.
Try Docapybara free. Start with one item that's been on your list too long, write the why and the next action, and see how much closer it feels by next month.