Relocation Playbook
The move is done. I turned the method into an open-source kit in September 2026.
An AI chief of staff for our move from Melbourne to Washington DC: one folder of plain text files that Claude Code turned into a plan, a weekly couples' agenda and a research queue. Now an open-source kit anyone can copy.
- Why
- An international move is dozens of problems that depend on each other, and I wanted to take the mental load off my partner. When a flight date moved, it rippled into the lease, insurance, sales and cash, and the AI kept all of that in one place.
- How long
- March to September 2026
How I built it
- I opened Claude Code in an empty folder and had it interview me about every part of the move: lease, jobs, health cover, documents, tax, shipping and selling.
- I had it write the plan as plain text files, ordered against our timeline.
- Before each weekly review with my partner, the AI built the agenda from the plan and whatever was most urgent.
- When the setup broke under pressure, I rebuilt it around a state folder: one small file per fact, each marked confirmed, assumption or recommendation, with its source and a date to re-check it.
- I added a wrap-up step that runs after every session, solo or shared, and builds the next agenda straight from those files.
- I published the method as a template with fictional examples.
- To copy it you need
- Claude Code, or the AI of your choice that can read and edit a folder of files. Optional: Notion for a task board. Gotcha: never let the AI keep facts in long prose summaries. Give every fact its own small record with a status and a re-check date, or it quietly rewrites them.
Try it yourself
Copy this prompt and paste it into ChatGPT or Claude to try it yourself.
I'm planning a big household project (a move, a renovation, a wedding) and I want to copy Korab Eland's Relocation Playbook from whatarewebuilding.ai (github.com/korabeland/relocation-playbook). Korab used Claude Code as a household chief of staff working from one folder of plain text files. Help me set up the same thing. Interview me about every part of my project first, one question at a time. Then create a state folder where every fact, deadline and decision gets its own small file, marked confirmed, assumption or recommendation, with its source and a date to re-check it. The gotcha Korab hit: prose summaries drift and a 'verified facts' file ended up holding a guess, so never store a fact twice. Start by drafting our first weekly agenda. Ask me for anything you need.
Tools I used for this project
