Asana Milestone and Dependency Realism Audit
Check whether the plan can actually work.
The Open buttons send the prompt text as currently shown below to that site only when you click. Fill in the placeholders first.
[VERIFY] is an editorial flag, not a blank to fill. Wherever the prompt shows [VERIFY], check that item against a reliable source before you use it.
Audit a project plan. Tasks with owners, durations, dependencies, milestones and deadline: [PLAN_DATA]. Team availability: [AVAILABILITY]. Working days assumed: [WORKING_DAYS]. List the tasks in order with duration and dependency, find the longest chain to get the earliest finish, and compare it with the deadline. Worked example: tasks A (5 days), then B (10), then C (4) in sequence take 19 working days; a task D (8) in parallel with B does not extend the plan, unless it needs the same person as B, in which case it does. Look for tasks with no owner, estimate or dependency, tasks in parallel that need the same person, and external dependencies. Check each milestone has a checkable condition, an owner, and tasks assigned before it that can actually reach it. Show all arithmetic and state your assumptions about working days. Return a table of findings and three options for meeting the date (cut scope, add capacity or move the date) with the effect of each. Treat menu paths and field names as unconfirmed until checked in my own instance, and show that with [VERIFY].
Fill in before use
Optional: type your details and the prompt above updates. Nothing is saved or sent.
Replace each bracketed placeholder with your own details, then paste into Any AI or another assistant.