agent sidequestsIdeas worth trying
Work & outreach

Remember who promised what, and what happened next

Keep a commitment ledger for a deal, dispute or contractor job: who promised what, the deadline and dated evidence. See what was kept, what is overdue and what needs confirming.

You get: A source-linked commitment ledger and a short review queueOriginal prompt · Not run-tested

Your copy-and-paste prompt

Read as Markdown

Replace the [brackets] with your details, then paste this into your assistant.

Build a commitment ledger for [deal, dispute, contractor job, project or shared responsibility] from [messages, notes or explicitly authorized sources]. Include only [people or roles, channels and date range]. Track my commitments as well as commitments made to me. Start with at most [20] items and put ambiguous statements in a separate review queue.

For each explicit promise, record who agreed to do what, for whom, when it was agreed, the actual due date and timezone if stated, the source link or message reference, and the latest dated evidence. Keep a request or hopeful suggestion separate from an accepted commitment. Do not invent a due date. If I add an item from memory, label it as my account until corroborated.

Use statuses such as open, kept, overdue, renegotiated, withdrawn, confirmed not kept, and unclear. Missing completion evidence means unconfirmed, not failed. Reserve confirmed not kept for explicit evidence or my confirmation; an overdue item is not automatically a broken promise. Preserve disagreements and the old deadline when an agreement changes. Judge the item, not the person's character or reliability.

Deliver an editable ledger plus a review of at most five items that need attention, with one factual next step each. Keep only information needed for this scope. For future updates, show changes and source references rather than rewriting history. If recurring checks are available, propose the sources, review cadence and notification rule for approval, then verify the saved setup; otherwise give me a reusable update prompt. Notify only on a meaningful status change or an agreed deadline threshold. Draft any nudge privately and get approval for the exact recipient and message before sending.

For a disputed item, preserve each party’s account and the supporting records. A ledger status records the available evidence; it does not decide legal liability.
What the result could look like

A promise with a visible paper trail

Illustrative only: a shared-project ledger could show an outline delivered on Tuesday, a budget review now overdue with completion unconfirmed, and a deadline explicitly moved to Friday. Each row points to the message that supports its status.

Illustrative example. This is not an observed result or a verified recommendation.

From the community

Inspired by a workflow shared by the site founder. This prompt is an original adaptation; it has not been run-tested.

Make it more you

Use it just for promises you make. Ask for a weekly list of commitments to finish, renegotiate or clarify, with draft messages for your review.

Keep the ideas coming

All sidequests
An ongoing helper

Wake up to a 6am brief that remembers yesterday

Combine your calendar, email and meeting notes into a short morning PDF. Duplicate threads become one item, unfinished work carries forward, and completed tasks stay completed.

You get: A dated morning PDF and a persistent action register with completion historyGet the promptCommunity-inspired idea