dependency-tracker

Cross-team dependencies are mapped by extracting explicit items from project artifacts like TASK_MASTER.md and PRDs, alongside implicit detection of task overlaps, to generate Mermaid visualizations and risk assessments.

Critical path risk assessment scores dependencies based on their probability of delay and impact, flagging high-risk items to proactively address blockers before a program release.

Yes, you can use PRDs for dependency discovery. The Skill utilizes explicit extraction from PRDs and TASK_MASTER.md, alongside implicit detection of inter-team task overlaps, to identify dependencies.

To map dependencies with overlapping tasks, the Skill performs implicit detection of inter-team task overlaps across project artifacts to maintain a central dependency map and identify potential risks.

Yes, dependency visualization works for release management by mapping and scoring cross-team dependencies to identify the critical path, generating visual representations to flag potential blockers.

The best way to manage cross-team dependencies is by maintaining a canonical dependency map that automatically discovers explicit and implicit overlaps, scoring risks to flag high-impact blockers before release.