When should you use it?
- Your todos live in seven tools
- You like managing tasks yourself
- Plans made days ahead never survive
Not for: Moving or closing tasks automatically; Teams that need a shared planning board
What do you need, and what do you get?
You need
- Read connections to calendar, tickets, email, docs, code and chat
- Your priority rules
You get
- Prioritized plan for today
- Meeting prep notes
- Local dismiss list
How does it work, step by step?
- Connect read-onlyGive the agent read scopes only for each tool.
- Gather todosPull open items from every source into one list.
- Reason about todayAsk it to order work by deadlines, blockers and meetings.
- Add your contextRaise or lower items using knowledge the tools do not hold.
- Dismiss locallyHide items such as old mentions in a local store, not at the source.
The prompt
Our own prompt, inspired by Kim Maida and written to work in Custom agent, Claude and Claude Code. Values in lime are placeholders.
Read my calendar, open Linear issues assigned to me, starred and unanswered Gmail threads, recent Slack mentions, open GitHub reviews and yesterday's meeting notes. Do not change anything. Propose a plan for today only: top three priorities with why, blockers to chase, and prep notes for each meeting. Skip anything on my dismissed list. Ask me if a priority depends on context you cannot see.
Inspired by Kim Maida: I Built and Authorized a Planning Agent with MCP and Keycard. The prompt above is written by playbooks.bot in our own words; nothing from the original is quoted.
What can go wrong?
- Write access tempts scope creep; the author deliberately kept it read-only.
- Planning beyond today wasted effort for her, since her days change hourly.
Our take
Thoughtful because it is clear about limits. Read-only access, one-day horizon and a local dismiss list keep the agent useful without letting it thrash your systems. Kim kept the agent to read scopes across every tool and a one-day horizon, and both limits are deliberate. Write access tempts scope creep, and plans for later in the week were wasted effort when her days changed hourly. The local dismiss list is a smart touch: hiding an old mention in the planner does not delete or close anything at the source. Start by connecting two or three tools, check the proposed order against your own sense of priorities, and add context the tools cannot know, such as a promise made in a hallway conversation. If the plan keeps putting the wrong things first, tighten the priority rules rather than granting more access. Teams that need a shared board will want something else; this is a personal planning aid.
Where the time goes back: It replaces the morning trawl through seven apps with one ordered list you can still overrule.
FAQ
Why not let it mark tasks done?
How are dismissals handled?
Source and credit
Inspired by Kim Maida. We describe the idea in our own words, link to the original, and wrote the prompt ourselves; nothing is quoted.
- Inspired by
- I Built and Authorized a Planning Agent with MCP and Keycard
- Creator
- Kim Maida
- Published on
- DEV Community
- Original date
- Mar 11, 2026
- License
- Not openly licensed (the poster keeps all rights), so we quote nothing and link to the original
- Originally for
- Custom agent
- AI dry run
- Oct 23, 2026: passed. Dry-run tested by our AI test agent on sample input. PASS: Gates held on desk check; no live sends or purchases.
AI dry run on sample data; not run with live connected accounts. The playbooks.bot test agent filled the prompt with synthetic inputs, produced the output and checked it against the page's stated outputs and guardrails. - Verified
- Oct 24, 2026: source link resolves to the original, the credited creator published it, our excerpt or prompt matches it, and the license allows our use.
Are you the creator? Claim or correct this page.