<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Agent Desk</title>
    <description>The latest articles on DEV Community by Agent Desk (@agentdesk).</description>
    <link>https://dev.to/agentdesk</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4211909%2F4e235a67-e1cb-4568-863f-4405c9174feb.png</url>
      <title>DEV Community: Agent Desk</title>
      <link>https://dev.to/agentdesk</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/agentdesk"/>
    <language>en</language>
    <item>
      <title>The daily plan rule file that stops my AI assistant from overplanning</title>
      <dc:creator>Agent Desk</dc:creator>
      <pubDate>Wed, 28 Oct 2026 02:15:07 +0000</pubDate>
      <link>https://dev.to/agentdesk/the-daily-plan-rule-file-that-stops-my-ai-assistant-from-overplanning-e1p</link>
      <guid>https://dev.to/agentdesk/the-daily-plan-rule-file-that-stops-my-ai-assistant-from-overplanning-e1p</guid>
      <description>&lt;p&gt;Ask an AI for a daily plan and you usually get a fantasy: eleven tasks, zero breaks, and a meeting it forgot about. A short rule file fixes that, because the assistant knows your hours, your goals, and when to stop.&lt;/p&gt;

&lt;p&gt;Copy this, fill in the square brackets, and save it as a saved instruction or skill in your assistant.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;NAME: Daily Plan
OWNER: [YOUR NAME]
WORK HOURS: [e.g. 9:00 to 17:30]
MY TOP GOALS THIS MONTH: [GOAL 1], [GOAL 2], [GOAL 3]

WHAT TO DO
1. Read today's calendar and my open tasks from [TASK SOURCE, e.g.
   my task app, notes I send you, flagged emails].
2. Suggest a plan for today with:
   My 3 most important tasks, and which monthly goal each one serves.
   Suggested time blocks around my meetings.
   One small admin task to clear.
   What to move or drop if the day gets busy.
3. Leave at least [1] hour unplanned for surprises.
4. Keep it short enough to read in one minute.

APPROVAL RULES
Never create, move, accept, or decline calendar events, and never
message anyone, without my explicit OK in this chat.
If you suggest calendar blocks, wait for "approved" before adding them.
If I say nothing, do nothing.

WHEN UNSURE
Ask me which task matters more instead of guessing.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;h2&gt;
  
  
  What makes it work
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Three tasks, not eleven.&lt;/strong&gt; A short list is a list you actually finish.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Every task is tied to a goal.&lt;/strong&gt; If a task serves nothing, it is a candidate to drop.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;An hour of slack.&lt;/strong&gt; Plans without slack fall apart at the first surprise.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Approval before calendar changes.&lt;/strong&gt; It suggests, you decide.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  How to start
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;Save the rule file and ask your assistant to repeat back in 3 lines what it will and will not do.&lt;/li&gt;
&lt;li&gt;Run it by hand for three mornings and compare it to the plan you would have made.&lt;/li&gt;
&lt;li&gt;Fix whatever it got wrong in the rule file.&lt;/li&gt;
&lt;li&gt;Then schedule it, for example weekdays at 8:00.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;This is one of three complete workflows in a free sample (inbox triage, daily plan, lead follow up), each with an example and a checklist: &lt;a href="https://payhip.com/b/pRHmP" rel="noopener noreferrer"&gt;free sample&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;What is the first thing you check when you plan your day?&lt;/p&gt;

</description>
      <category>ai</category>
      <category>productivity</category>
      <category>beginners</category>
      <category>workflow</category>
    </item>
    <item>
      <title>The inbox rule file I give my AI assistant (copy and paste)</title>
      <dc:creator>Agent Desk</dc:creator>
      <pubDate>Wed, 28 Oct 2026 01:28:36 +0000</pubDate>
      <link>https://dev.to/agentdesk/the-inbox-rule-file-i-give-my-ai-assistant-copy-and-paste-ebc</link>
      <guid>https://dev.to/agentdesk/the-inbox-rule-file-i-give-my-ai-assistant-copy-and-paste-ebc</guid>
      <description>&lt;p&gt;Most AI inbox advice is "just ask it to summarize your email". That works once. A saved rule file works every day, because the assistant never has to guess what you want.&lt;/p&gt;

&lt;p&gt;Here is the one I use. Copy it, fill in the square brackets, and save it in your assistant as a saved instruction or skill.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;NAME: Inbox Triage
OWNER: [YOUR NAME]

WHAT TO DO
1. Read all unread email received since the last run.
2. Sort each email into one of four groups:
   URGENT: needs my reply or action today (clients, payments, deadlines).
   REPLY: needs a reply this week.
   READ LATER: newsletters, updates, FYI.
   IGNORE: promotions and automated notices.
3. For each URGENT and REPLY email, give me:
   sender, subject, one sentence summary, and what they want from me.
4. Draft a reply for each URGENT email in my tone: [YOUR TONE, e.g.
   friendly, short, direct]. Keep drafts under 120 words.
5. Put the list in this order: URGENT, REPLY, then just a count of
   READ LATER and IGNORE.

VIP SENDERS (always URGENT)
[NAME OR DOMAIN 1]
[NAME OR DOMAIN 2]

APPROVAL RULES
Never send, reply, forward, archive, delete, or label any email
without my explicit OK in this chat.
Show me every draft in full first.
Only send a draft after I reply "approved" or "send it" for that email.
If I say nothing, do nothing.

WHEN UNSURE
If you cannot tell which group an email belongs in, put it in REPLY
and say why you were unsure.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;h2&gt;
  
  
  Why it works
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Four groups, not ten.&lt;/strong&gt; Fewer buckets means fewer wrong guesses.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;A hard approval block.&lt;/strong&gt; The assistant drafts, you decide. Nothing leaves your inbox without your "approved".&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;A "when unsure" rule.&lt;/strong&gt; Doubtful emails land in REPLY instead of silently disappearing.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  How to use it
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;Save the rule file and ask your assistant to confirm in 3 lines what it will and will not do. Fix any misunderstanding now.&lt;/li&gt;
&lt;li&gt;Run it by hand three times and compare the result to what you would have done.&lt;/li&gt;
&lt;li&gt;Edit the rule file where it got things wrong.&lt;/li&gt;
&lt;li&gt;Only then put it on a schedule, for example weekdays at 8:30.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;I wrote a free sample with 3 complete workflows (inbox triage, daily plan, lead follow up), each with an example and a checklist: &lt;a href="https://payhip.com/b/pRHmP" rel="noopener noreferrer"&gt;free sample&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;What is the one admin task you would hand to an assistant first?&lt;/p&gt;

</description>
      <category>ai</category>
      <category>productivity</category>
      <category>beginners</category>
      <category>automation</category>
    </item>
  </channel>
</rss>
