Parent Runbook

Ask first

• Which sources may it read? (default your inbox, your texts, and notes from meetings if you keep them; ignore newsletters and automated mail)
• Who counts as someone you owe or who owes you? (default anyone who wrote to you personally in the last 60 days)
• When is a promise stale? (default 30 days, or 60 days if it has no date)
• Where should the list live? (default one page you open each morning)

Needs

• Read access to the sources
• One saved list with these fields for every item: title, who, direction (mine or theirs), source and link, date captured, due date if any, confidence (high or low), status (open, done or dropped) and why it closed
• A scheduler that can run every 15 minutes
• If your assistant cannot read one of these, paste it when it asks. A thinner version still works
• Any password or token is entered by you into your device's secure store, never pasted into a chat or saved in a plain file

Build

1. Every 15 minutes, read messages and notes added since the last run. Pick out sentences where someone commits to do something: "I will", "I'll send", "we'll have it by", "can you send me".
2. Save each as one item with every field above. Mark confidence low if the commitment is vague or the date is a guess.
3. When a later message in the same thread contains the promised thing (an attachment, a link, the words "here it is"), close the item and write why. Never close an item on silence.
4. Mark an item stale after the stale limit and move it to a dropped list, never delete it.
5. Show the list with days waiting, oldest first, amber after seven days. This one list is the source for every other run that needs promises: the morning brief reads its Due from you section from it, and the follow-up run adds each commitment it drafts to it.

Check

• Seed three promises in a test thread; confirm all three appear with the right direction and date
• Send the promised thing; confirm the item closes and says why
• Confirm a vague promise is marked low confidence and a stale one moves to the list of dropped items
• Say whether the writing step ran for real or on sample text. Check that every figure, quote and link matches its source, and drop any that does not

In my version

• Claude Code on a 15-minute schedule, one list I open each morning; my morning brief and my follow-up run both read and write it

Ask first

• What are the pickup times?
• Who could collect if you cannot?

Needs

• Read access to the calendar and a list of pickup times
• If your assistant cannot read one of these, paste it when it asks. A thinner version still works
• Any password or token is entered by you into your device's secure store, never pasted into a chat or saved in a plain file

Build

1. Every 15 minutes, compare today's meeting end times to the pickup time.
2. If a meeting could overlap, write the clash and two options.
3. Warn when a meeting ends within 30 minutes of pickup plus your travel time. Defaults: 30 minutes, and 15 minutes of travel. Never message anyone until I reply A or B.

Check

• Put a test meeting over a pickup time; the warning arrives
• Confirm nothing is sent without a reply
• Say whether the writing step ran for real or on sample text. Check that every figure, quote and link matches its source, and drop any that does not

In my version

• Claude Code on a daytime schedule, a text with two options

Ask first

• What is your gift budget?
• Who may it reply to? (default nobody; it only reminds you)

Needs

• Read access to the inbox and calendar
• If your assistant cannot read one of these, paste it when it asks. A thinner version still works
• Any password or token is entered by you into your device's secure store, never pasted into a chat or saved in a plain file

Build

1. Every hour, look for new invitations. Keep a list of the items already handled (by their address or id) and skip any that are on it, so the same item never produces a second brief, comment or draft.
2. Add each to the calendar with its reply-by date.
3. Suggest a gift based on the child's age and what you know they like, and check it fits the budget.
4. Never reply for me.

Check

• Send a test invitation; the entry and reminder appear
• Confirm no reply was sent
• Say whether the writing step ran for real or on sample text. Check that every figure, quote and link matches its source, and drop any that does not

In my version

• Claude Code hourly, a calendar entry and a text

Ask first

• Which schools or senders?
• Where should dates go?

Needs

• Read access to school email and the calendar
• If your assistant cannot read one of these, paste it when it asks. A thinner version still works
• Any password or token is entered by you into your device's secure store, never pasted into a chat or saved in a plain file

Build

1. Every hour, read new mail from the schools. Keep a list of the items already handled (by their address or id) and skip any that are on it, so the same item never produces a second brief, comment or draft.
2. Pull out each date, form and fee.
3. Add it to the calendar with the form attached and a reminder two days before.
4. Skip anything with no date. Mark each message handled so the document-summary run skips it and no school form reaches you twice.

Check

• Send a test school email; the date and reminder appear
• Confirm a message with no date is ignored
• Say whether the writing step ran for real or on sample text. Check that every figure, quote and link matches its source, and drop any that does not

In my version

• Claude Code hourly, entries on the family calendar

Ask first

• What time should it arrive? (default 7am on weekdays, your time zone)
• Which calendars and inboxes count? (default your work calendar and work inbox)
• Which accounts or customers should it watch? (default any that wrote to you in the last 30 days)
• Where should it land? (default a page you open, or a message from your assistant)

Needs

• Read access to your calendar and inbox
• A short list of accounts to watch, or a way to infer them from recent mail
• The promises list, if you keep one. If you have none, build it by pulling "I will" and "I'll send" lines from your last 14 days of sent mail, or paste one in
• If your assistant cannot read one of these, paste it when it asks. A thinner version still works
• Any password or token is entered by you into your device's secure store, never pasted into a chat or saved in a plain file

Build

1. Each weekday before the set time, read today's events, unanswered mail from the last three days, and any change in the watched accounts since yesterday.
2. Write one page with four parts: Today, Needs you, Moved overnight, Due from you. Read Due from you straight from the promises list; do not rebuild it from mail. Keep each part to at most five lines.
3. If a part is empty, leave it out.
4. Put the page where you read it. Never send anything on your behalf.

Check

• Run it once now and confirm each line names a person or an account, not a general remark
• Confirm nothing on the page is more than three days old unless it is a promise
• Confirm Due from you matches the promises list
• Say whether the writing step ran for real or on sample text. Check that every figure, quote and link matches its source, and drop any that does not

In my version

• Claude Code on a weekday schedule at 7am, written to one page I open in the browser

Ask first

• What time should it arrive? (default 15 minutes before the first person wakes)
• Whose calendars count? (everyone in the house)
• Weekends too? (default only if there is an early event)
• Who drives each leg? (default read from a shared driving note, one line per child per day; if none is set, the text says "driver not set")

Needs

• Read access to the calendars and school email, or a weekly paste
• If your assistant cannot read one of these, paste it when it asks. A thinner version still works
• Any password or token is entered by you into your device's secure store, never pasted into a chat or saved in a plain file

Build

1. Before the set time, read today's events for each person.
2. Add what each needs to bring and what is due.
3. Say who drives each leg.
4. Write one short text, one line per person.

Check

• Run it for tomorrow; every line matches a calendar entry
• Confirm nothing is added that is not in a source
• Say whether the writing step ran for real or on sample text. Check that every figure, quote and link matches its source, and drop any that does not

In my version

• Claude Code on a weekday schedule, a text to me

Ask first

• Which day and time to check? (default Friday 8am, your time zone)
• How you want the picks? (default the place you already hear from your assistant)
• How many picks at most? (default 3)

Needs

• An assistant that can run on a schedule and open a web page
• What your assistant already knows about you: your routines, tools and recurring tasks
• If your assistant cannot read one of these, paste it into the chat when it asks. A thinner version still works

Build

1. Each week, open the Runbook list of new runs since the last check.
2. Pick at most three that fit something specific about the person. Skip ones they already have or that need a setup they lack.
3. If nothing fits, send nothing. Otherwise send each pick's name, one line on why it fits and its link.
4. Never build anything without a yes. On a yes, open that run's build steps and follow them.
5. Save the date of this check.

Check

• Run it once with since set to 30 days ago and delivery off; every pick names a specific reason it fits
• A week with nothing new sends nothing
• Say whether the writing step ran for real or on sample text. Check that every quote and link on the page matches its source, and drop any that does not

In my version

• Claude Code on a schedule, Fridays at 8am, picks sent to my assistant

Ask first

• Which stores' order history can it read? (default: the one or two you buy household staples from)
• How often should it look? (default: weekly)
• Most nudges per week? (default: 3)
• Should "add it" put the item in your cart, or just remind? (default: remind only)

Needs

• Order history with item names and dates, at least 6 months. Most stores have an order history page or an export; if not, a year of order-confirmation emails works.
• If your assistant can only chat: paste your last few orders once a month and ask "what am I likely to run out of in the next week?"; it does the same arithmetic.

Build

1. Read: weekly, refresh the order history and group purchases by item.
2. Decide (rhythm): an item has a rhythm once it has been bought 3 or more times. The interval is the days from first to last order divided by orders minus one. Keep items with an interval between 45 and 150 days (vitamins, filters, diapers); faster is groceries, slower is "buy when it breaks". Skip fee lines.
3. Decide (due): an item is due when its last order plus the interval falls within the next 7 days. If it is more than 1.75 intervals overdue, treat it as abandoned and stay quiet. Skip anything already nudged and still open.
4. Decide (cap): at most 3 nudges per sweep, most overdue first.
5. Deliver: one message per item: "Running low on X? Last ordered 58 days ago, you usually reorder every 60." If you set up cart adds, "add it" adds it; checkout stays with you.

Check

• Run on your history with delivery off; every item must show 3 or more orders and its interval.
• Pick an item you stopped buying a year ago: it must not appear.
• A week with nothing due sends nothing.

In my version

• Order history from my main online store, refreshed weekly; nudges go to my assistant's text thread

Ask first

• Anyone who cannot eat something?
• Which nights are busiest? (default read from the calendar)
• Where is the shopping list kept?
• How does it know what is at home? (default a pantry note you update on Sundays; if none, assume nothing is there)

Needs

• Read access to calendars and a list of preferences
• If your assistant cannot read one of these, paste it when it asks. A thinner version still works
• Any password or token is entered by you into your device's secure store, never pasted into a chat or saved in a plain file

Build

1. Each Sunday, read next week's events and who is late.
2. Pick quick meals for late nights and nicer ones for free nights.
3. Add up what is needed less what is at home.
4. Never place an order.

Check

• Run it for next week; nobody is served something they cannot eat
• Confirm the list matches the meals
• Say whether the writing step ran for real or on sample text. Check that every figure, quote and link matches its source, and drop any that does not

In my version

• Claude Code on a Sunday schedule, a plan in our family note

Ask first

• Whose calendars count? (everyone in the house)
• What needs a plan? (default anything with a time and no name beside it for who is taking them)

Needs

• Read access to the calendars and a list of who normally does what, or paste next week
• If your assistant cannot read one of these, paste it when it asks. A thinner version still works
• Any password or token is entered by you into your device's secure store, never pasted into a chat or saved in a plain file

Build

1. On Sunday evening, read next week's events for everyone.
2. For each, check it has what it needs: who drives, who is bringing what, anything due before it.
3. List the gaps and any two events that overlap for the same person.
4. Draft the smallest fix for each, only on a reply. Send one text.

Check

• Run it on a week you know; at least one gap it finds is real
• Confirm an event with all it needs is not listed
• Say whether the writing step ran for real or on sample text. Check that every figure, quote and link matches its source, and drop any that does not

In my version

• Claude Code on a Sunday schedule, a text

Ask first

• What counts as long? (default over 400 words or any attachment)
• Which sources? (default your inbox and one shared folder)
• Where should the card land? (default a page you open)

Needs

• Any password or token is entered by you into your device's secure store, never pasted into a chat or saved in a plain file
• Read access to mail, attachments and the folder
• Somewhere to write a card per item with a link back
• If your assistant cannot read one of these, paste it into the chat when it asks. A thinner version still works

Build

1. Every 15 minutes, look for new long items you have not summarised, skipping any marked handled by another run, and read each fully.
2. Write a card: what it is, what it asks of you, dates, and what you would push back on. Under 80 words.
3. Link the original. Mark anything with a date in the next seven days.
4. Never reply or forward.

Check

• Run it on a document you know well; every date on the card is in the document
• Confirm a short email is skipped
• Say whether the writing step ran for real or on sample text. Check that every quote and link on the page matches its source, and drop any that does not

In my version

• Claude Code on a schedule, cards written to a page I open each morning

Ask first

• Which days are handover days?
• What does each child always need?

Needs

• Read access to the calendar and a note of what each child always needs
• If your assistant cannot read one of these, paste it when it asks. A thinner version still works
• Any password or token is entered by you into your device's secure store, never pasted into a chat or saved in a plain file

Build

1. On handover mornings, read each child's week ahead.
2. List what is needed from the events.
3. Add anything left behind last time.
4. Send one text. At 8pm on each handover day, ask what was left behind and save it, so the next list never starts empty.

Check

• Run it for a handover day; every item ties to an event or a note
• Confirm last time's leftovers appear
• Say whether the writing step ran for real or on sample text. Check that every figure, quote and link matches its source, and drop any that does not

In my version

• Claude Code on handover mornings, a text