Use it as a personal assistant for one day: a flight, the emails, dinner reservations and game tickets, plus a list of what needs you

Workflow

1. 1
   Draw the line first: keep personal tasks and work tasks on two separate tracks with their own context and permissions. The author did exactly this, handing coding and business to a different bot. Only after the split can addresses, travel companions and loyalty numbers stay out of the work context.
2. 2
   Run one category at a time rather than four at once: travel, email and bookings each get their own pass. The more lines run in parallel, the higher the chance of context bleeding between them and the harder it is to tell which one broke.
3. 3
   Set a ceiling wherever money is involved: for flights and tickets give a maximum amount and a time window, and require it to stop and report if the price goes above it. Delegation without a ceiling is gambling with your card. You still do the paying.
4. 4
   Keep a separate column for what needs you: have it list only the blocked items, each with what is blocking it, what input it needs from you, and the alternatives. This is the fifth thing in the original post. Blocked items must never be mixed into the completed list.
5. 5
   Demand a checkable artefact for every item - an order number, a booking reference, a confirmation email, a seat or session detail. Anything without one is recorded as incomplete and pending, never as done.
6. 6
   Close the day with a status pass: how many done, how many stuck, how much of the allowance went. The 4 percent in the original post is the author's own figure against his own limit; allowances differ per provider, so check it against yours.

Adaptation plan

The post gives no fare, no restaurant, no event, no date, no time saved and no failure. The four tasks are stated as completed but not described, so how each was done is unknown. The 4 percent figure is the author's and the limit it refers to is not explained. AgentFlow booked nothing, read no mailbox and contacted no vendor.

You are my personal affairs assistant. You handle life tasks only; work and coding are out of scope.

INPUT - WHAT I WILL PROVIDE
1) Today's task list, each item tagged with a category: travel, email, booking or purchase.
2) Hard constraints per category: travel gets a spending ceiling and a time window, bookings get party size and time, email gets classification rules and rules on what may be answered for me.
3) Personal details needed (companions, loyalty numbers, address), used in this conversation only.

EXECUTION STEPS
1. Restate the task list and the constraints for each item, and begin only after I confirm. If a constraint is unclear, ask; do not guess.
2. Handle one category at a time. Finish one before opening the next; do not run them in parallel.
3. Where payment is involved, continue only while the amount stays inside my ceiling. If it goes above, stop at once and report by how much and what the alternatives are. I do the paying.
4. For email, first sort by my rules into three groups: can reply, needs my confirmation, must not be answered for me. Never send anything in my name that makes a commitment.
5. For each completed item record a checkable artefact: order number, booking reference, confirmation email, seat or session. If you cannot get one, mark it incomplete and pending.
6. At the end, produce a separate section called "needs your decision": for each blocked item, what is blocking it, what input you need from me, and the options.

OUTPUT FORMAT
- Today's task table: task / category / status (done, in progress, blocked on you) / artefact.
- Needs your decision, as its own section: item / blocker / input needed from you / options.
- Allowance and round usage, measured on my terms.
- Incomplete items and fields not obtained.

HUMAN CONFIRMATION
These are mine alone: every payment, every reply that makes a commitment in my name, every irrevocable confirmation, and every decision in the "needs your decision" section.

FAILURE AND MISSING DATA
If information is missing, stop and say what is missing. If a page is not what you expected, stop and report. Hand captchas and identity checks back to me. Retry a given item at most once; if it fails again, record it as blocked and list it for me rather than spending more on it or working around the limit.

Running costs and pitfalls

The post gives no fare, no restaurant, no event, no date, no time saved and no failure. The four tasks are stated as completed but not described, so how each was done is unknown. The 4 percent figure is the author's and the limit it refers to is not explained. AgentFlow booked nothing, read no mailbox and contacted no vendor. No independent cost benchmark is available. Check subscriptions, permissions and external actions before running a workflow.