Stack: Claude (Pro, web or desktop) + the Asana MCP connector
The slip happens at the moment of the promise, not months later when you notice it.
Somebody asks whether the integration can land by Thursday the 14th. You look at the task, it is two days of work, and you say yes. What you did not look at is that the engineer who owns it already has six other items due that same week, three of which are also two-day jobs. The date was never achievable. You committed to it anyway, because the information that would have stopped you was spread across four project views and nobody assembles that in the middle of a call.
This method answers one narrow question in about a minute: can this person absorb a new deliverable due on this date, given everything already pointed at that week?
It does not plan your project. It does not level your resources. It gives you a number before you open your mouth.
Three things make the naive version of this useless, and the phases below exist to handle them.
Load is not inside your project. The person you are about to commit is also on two other projects run by two other managers. A check scoped to your project returns a confident answer to a question nobody asked. Phase 3 widens the scope, and it is the phase people skip.
Missing data reads as free capacity. If a third of the open tasks have no due date, the weeks look empty because the work is unscheduled, not because the person is available. This failure is silent and it points in the dangerous direction. Phase 1 exists entirely to catch it, and on some projects Phase 1 is where you stop.
Task count is not effort. Base Asana has no estimate field. A week with two large tasks can be worse than a week with seven small ones. Phase 4 calibrates against each person's own history instead of inventing a universal threshold.
It sees Asana and nothing else. Meetings, interviews, on-call rotations, leave, and work that lives in a different tool are invisible to it. A week that looks clear here can be fully booked in reality.
It produces a candidate for a conversation, not a verdict. The output of a good run is "this week looks heavy for Priya, go ask her," not "the date is impossible."
List every Asana tool you currently have available. For each one, give me the exact tool name and its full parameter list. Do not call any of them yet.
The Asana connector is thinner than most project connectors, roughly fifteen tools, and names change between server versions. Asana's own documentation tells clients to enumerate at runtime for that reason.