← Back to library

Plan today across work tools with a read-only agent

Kim Maida, whose day spans calendar, Linear, Gmail, Docs, GitHub, Slack and meeting notes, built a planning page whose embedded assistant only reads those tools and proposes a plan for today. It never marks work done and keeps a local dismiss list.

  • OutcomeGet one prioritized view of today's tasks, blockers and meeting prep drawn from all your tools, without the agent changing anything at the source.
  • SetupAn afternoon+
  • LevelAdvanced
  • CreditKim Maida
View original
Works with
Custom agentClaudeClaude Code

Published Oct 23, 2026Updated Oct 23, 2026AI dry run on sample input: passed Oct 23, 2026Source verified Oct 24, 2026

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?

  1. Connect read-onlyGive the agent read scopes only for each tool.
  2. Gather todosPull open items from every source into one list.
  3. Reason about todayAsk it to order work by deadlines, blockers and meetings.
  4. Add your contextRaise or lower items using knowledge the tools do not hold.
  5. 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.

Prompt0 variables
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?
The author likes checking things off herself and wanted planning help only.
How are dismissals handled?
A local store records what she dismissed when the source tool cannot.

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.

More in Operations & Admin

All 203 Operations & Admin playbooks →

Related playbooks

Operations & AdminPrompt✓ AI dry run

Give your agents one shared wiki that only one agent edits

Replace scattered agent memories with a single Markdown wiki in git: every agent reads a short daily brief from it, agents and scripts file sourced notes into an inbox instead of editing pages, one steward agent checks and merges those notes each morning, and private agent memory keeps only personal preferences.

Credit: Siim Tolk

An afternoon+
Operations & AdminWorkflow✓ AI dry run

Add a merge check for every way coding agents break code

Keep a running list of the specific ways coding agents have damaged your repository, from hollow tests and invented fake responses to deleted files and silenced type errors, and turn each one into an automated gate that blocks the merge, so the same mistake cannot slip through review twice.

Credit: u/alexmarquardt on r/ClaudeCode

An afternoon+
Operations & AdminWorkflow✓ AI dry run

Ask Reddit's experience before you pick a library

Let your coding agent search Reddit for long-term user reports on a library, an error message or a competitor before you commit to a choice.

Credit: u/karanb192 on r/ClaudeCode

Minutes
Operations & AdminRoutine✓ AI dry run

Unused subscription tokens become small PRs to review

Let a scheduled bot check your remaining subscription quota before the weekly reset and use it to open small PRs toward the goals and to-dos you list.

Credit: ariwilson on Hacker News

Under an hour