dependency-risk-check

What it does

The first useful run is a shortlist of the dependencies most likely to break the handoff: missing owners, overdue items, and blocked work. That gives the plan a usable repair path immediately.

Try it locally

python3 dependency_risk_check.py sample_plan.json --today 2026-04-15

Example output

Total items: 4
Open items: 3
Completed items: 1
Missing owners: 1
Overdue items: 2
Blocked items: 1

Missing owners:
- Write migration runbook

Blocked items:
- Analytics cutover <- warehouse-backfill [open]

Where it helps

Use this before launch reviews, cross-team rollout meetings, or anywhere the plan keeps sounding clean until somebody asks what is already late or who is actually carrying the dependency.