The critical path you drew at kickoff is not the one you are on now. Husn keeps it current from the work and tells you when the path itself shifts.
Husn reads your tools - never changes them
A critical path is usually mapped once, early, and then quietly diverges from reality as the work moves. The item you are watching most closely may no longer be the one that decides the date, and the item that now does may be one nobody is watching at all.
The path runs through work owned by several teams, so a slip on one board changes the constraint without anyone updating the plan.
Slack is what makes a task non-critical, and slack erodes silently, so the moment a task joins the critical path passes unobserved.
Recomputing the path means knowing the true state of every task on it, which no single person has across a large program.
Husn reads and reasons, and never changes your tools.
See which task is actually deciding your date today, instead of watching the one that was critical at kickoff.
Get flagged the moment a task with shrinking slack joins the critical path, before it silently becomes your constraint.
When the end date moves, see exactly which task on the path caused it and which team owns that task.
It reads the live state of the work across Jira, Slack, and docs and recomputes the path as tasks move, rather than holding the plan you drew at kickoff.
Yes. When a task's slack erodes and it moves onto the critical path, Husn flags it, so you learn about the new constraint as it forms.
It does. Husn follows the path across team boundaries, so a slip upstream reaches you as a warning about your own delivery date.
No. It reads only. Husn never changes dates, reschedules tasks, or writes anything back to your tools.
Connect your tools and Husn will keep your critical path current and flag every task that threatens your delivery date, in about fifteen minutes.