Find the work that threatens a milestone
An Asana portfolio can look healthy while an important milestone depends on an overdue task, an unassigned approval, or work with no current status. An agent can inspect selected projects and trace those dependencies into a portfolio risk brief.
Define the projects, reporting date, milestone window, and risk rules. Ask the agent to distinguish a late task from a delivery risk. A low-impact housekeeping task should not receive the same attention as a blocked approval on the launch path.
The result should cite the project, milestone, task, owner, due date, dependency, and latest relevant status. Missing ownership or stale updates are findings in their own right; the agent should not invent progress from task completion percentages.
Put the recovery plan on the calendar
Asana shows the work and deadlines. Google Calendar shows the meetings, decision points, and available time before those deadlines. A combined agent can prepare a checkpoint plan around the risks, making sure the right decision happens before the milestone rather than at the next routine status meeting.
Calendar changes should remain drafts. The project owner decides whether a risk needs a meeting, focused work time, an asynchronous update, or a changed due date.
