How an AI agent can turn a task list into a time-aware weekly plan
This workflow gives an AI agent a defined job, a bounded set of records, and a result a person can review. The agent reads the relevant Todoist context and matches it with Google Calendar, applies the rules in the prompt, and keeps the source behind every recommendation. It returns a proposed handoff rather than taking consequential actions on its own.
Can an AI agent turn a task list into a time-aware weekly plan?
Yes. Start with the scope, date range, decision rules, and fields that identify the right records. The agent can collect the evidence, compare states or sources, mark conflicts and missing data, and organize the result around the outcome above. A reviewer then checks the matches and judgment calls before approving messages, record updates, bookings, purchases, publishing, or other write actions. The guide below shows the records, boundaries, prompt, and handoff needed for this specific workflow.
Match task shape to calendar capacity
Todoist supplies the accepted tasks, priorities, deadlines, labels, and any available effort estimates. Google Calendar supplies fixed meetings, travel, personal constraints, and open time. The pair can build a plan that answers a concrete question: which tasks fit this week, which need a smaller next action, and which commitments require a deadline or scope conversation?
Set working hours, protected time, minimum focus-block length, buffer rules, and calendars in scope. Identify tasks that require a particular place, collaborator, or time of day. If a task has no estimate, the agent should flag it or use an estimate explicitly supplied in the prompt.
Example starter prompt
Use Todoist and Google Calendar to plan [date range] in [timezone]. Use tasks from [project or label] that have already been approved for this week.
Respect [working hours], [protected periods], and [buffer rules]. Match each task's estimate, deadline, location, and focus needs to available time. If the week cannot hold all approved work, show what does not fit and the decision required.
Do not change tasks or create calendar events. Return proposed focus blocks with task links, duration, rationale, and conflicts.Inspect the plan for hidden overload
Check that Google Calendar events are interpreted in the correct timezone and that tentative or all-day events follow the owner’s rules. Then confirm that each proposed block maps to the intended Todoist task and leaves enough time for the task’s actual next action.
Questions this workflow answers
Can my priority tasks fit into this week without overbooking the hours between meetings?
The agent begins with tasks the owner has already accepted for the week and calendar rules for working hours, protected time, buffers, travel, and minimum focus blocks. Each task needs a concrete next action, estimate, deadline, location or collaborator constraint, and link. Missing estimates stay visible instead of being squeezed into whatever opening remains.
Blocks are matched by shape as well as duration. Deep work should not be split into scattered fifteen-minute gaps, while a short administrative task may fit between meetings. The agent accounts for timezone, tentative and all-day events, transition time, and the energy or time-of-day constraints the owner explicitly provides. It does not infer personal productivity patterns from the calendar.
When demand exceeds capacity, the plan shows unscheduled work and the decision required: reduce scope, renegotiate a deadline, delegate, or move a lower priority. It does not hide overload by double-booking or trimming estimates. The handoff reports proposed blocks, total focus time, unscheduled tasks, deadlines at risk, and assumptions. Task edits and calendar events remain drafts until the owner approves each system separately.
The handoff should include scheduled proposals, unscheduled work, total planned focus time, and any deadline at risk. Task updates and calendar creation should use separate approvals.
The plan should use usable focus windows, not every white space on the calendar. A 45-minute gap between meetings may be enough for review but not for a two-hour design task once transition and preparation are included. The agent can respect working hours, energy preferences supplied by the user, location, deadlines, dependencies, and minimum block size. It should show the estimate behind each placement and leave overflow visible. The owner can then change priority or scope instead of accepting a calendar that promises more work than the week contains.