The follow‑up rule file that stops my AI assistant from forgetting loose ends

Description and use

The author built a rule file for an AI assistant to track open email threads, promises, and polite nudges, producing a concise table of tasks and draft replies while requiring manual approval before sending.

Problem

An AI assistant treats each email as a separate message and does not track open threads, promises, or polite nudges, leading to forgotten follow‑ups.

Outcome

The workflow keeps the author’s follow‑ups organized, ensures timely nudges, and limits the list to manageable size, all without sending any messages automatically.

Workflow

• Paste the rule file once at the start of the chat or save it as a custom instruction.
• Each morning paste yesterday’s sent and received message subjects or a short note list.
• Read the generated table and reply to the top item first.
• Copy the drafted nudges you agree with and delete the rest.
• Once a week clear the "Parked" list.

Evidence

An assistant sees each message on its own. It does not track: Threads where I promised something. Threads where someone else owes me an answer. When it is polite to nudge.

Source

FOLLOW-UP RULES 1. When I share messages or notes, list every open thread in a table: Thread | Who owes the reply | Due date | Next step 2. "Open" means: a question nobody answered, a promise not yet kept, or a request with no confirmation.

Source

Each morning, paste yesterday's sent and received message subjects, or a short note list.

Source

It drafts, it does not send. That is on purpose.

Source