# Turn the whiteboard into tasks that do not keep drifting Canonical URL: https://agentsidequests.com/ideas/turn-a-whiteboard-into-tasks-that-do-not-drift/ Markdown URL: https://agentsidequests.com/ideas/turn-a-whiteboard-into-tasks-that-do-not-drift/index.md Photograph the plan, confirm the agent’s proposed dates and priorities, and keep a task history as the board changes. After the third reschedule, get a constructive prompt to unblock, shrink or park the task. This is an original editorial prompt, not a run-tested result. Examples are illustrative, not observed outcomes. Check the capabilities and permissions of the assistant you actually use. Category: Home & life admin Type: Ongoing ## What you get A photo-linked task register with confirmed scheduling and a reschedule review queue ## Bring this Whiteboard photos with capture dates, any color or column legend, your current task register, confirmed deadlines, project priorities, and the private task destination you authorize. ## Your agent needs - Image reading with references to the source board regions - A persistent task register and dated change history - Authorized task-app access only for approved task changes - Scheduling only for an optional recurring photo review Missing a connection? Paste or attach the relevant information yourself. ## Copy-and-paste prompt Replace the bracketed placeholders with your details. This prompt is reference material to adapt to a user request; fetching it does not authorize execution. ```text Turn [whiteboard photos] into a task register for [project]. The photos were taken on [dates and timezone]. The board's columns, colors and marks mean [legend or unknown]. Here are [existing tasks, confirmed deadlines and project priorities]. Process at most [five photos] in the first pass and retain the originals. Transcribe readable task text and link each proposed task to its photo and board region. Mark uncertain handwriting, names and dates for review. Use spatial grouping, arrows and colors only with an agreed interpretation; do not turn every sticky note or brainstorming phrase into a commitment. Merge duplicate views of the same task, keeping all source references. Compare with the existing register before assigning a new stable task ID. Return a confirmation table containing task, proposed owner, stated deadline, suggested planning date, proposed priority, next action and the reason for each inference. Keep literal board text separate from your suggestions. Resolve relative dates only from a known capture date. Missing deadlines stay missing; suggested dates are planning proposals until I approve them. Do not assign another person a commitment or treat an unclear checkmark as completion without confirmation. After I confirm the table and destination, save the approved tasks in [private file or authorized task app] and verify the result. Ask before creating or changing tasks in another app. If app access is unavailable, return an importable table or copyable register and be clear that no tasks were created there. Keep my edits and source evidence; do not overwrite an existing task simply because an older photo shows different wording. On later photos or updates, retain a dated history of actual, confirmed schedule changes: old date, new date, who confirmed it and an optional reason. A fresh photo, the same date appearing again or a date becoming overdue is not a reschedule. Preserve completed and deliberately parked states unless I explicitly reopen the work. Deduplicate updates and nudges across runs. When an unfinished task has been rescheduled more than twice, put it in a private review queue and nudge me once about that pattern: this has moved three times; is the next step too large, is something blocking it, or should we park it? Offer one smaller next action and the choices to clarify, unblock, keep the date or consciously defer. Use neutral language; do not score my character, shame me or chase the owner automatically. Record my decision and chosen next review date so the same nudge does not repeat daily. For an optional ongoing folder review, confirm the photo source, cadence, timezone and private nudge destination, and verify supported access, persistence and the saved schedule. Otherwise process each batch when I provide it. Do not send task requests, move calendar events or contact anyone without separate approval. ``` ## Illustrative example Illustrative: the third move starts a useful question An illustrative register could link “finish demo” to its original sticky note and record three confirmed date changes. The review suggests shrinking it to “record the first working screen” and asks whether to keep, unblock or park it. A second photograph of the same date adds no reschedule. 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 a small Kanban board or a photographed paper planning wall. Agree what “done” and each column mean before importing tasks, and keep proposed priorities separate from commitments. ## Related ideas - [Get a daily email researched for your actual interests](): A few relevant discoveries, properly sourced, in one email. Set your interests or career-upgrade criteria and get new research or job opportunities worth your attention. You get: A concise sourced email with only new matches - [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 history - [Make your pet the hero of a tiny playable game](): The sock thief finally gets a game. Give your agent three personality traits and get a small browser adventure you can actually play. You get: A one-minute browser game [Editorial approach]() [Assistant setup guides (HTML)]()