What it proves
A planning utility can be valuable when it turns hidden dependency trouble into a visible repair list before the meeting starts.
Planning artifacts
dependency-risk-check is the cleanest example of a planning tool exposing the risk that usually hides in the middle of the handoff.
This guide exists because plans often look clean until someone asks who owns the late item, what is blocked, and which dependency is about to break the schedule. The repo makes that risk visible without pretending to replace planning.
Why this repo carries the track
A short site-side guide before the proof layer on GitHub.
Why it matters in this track
It extends the planning-artifact idea from one-page drafts into execution risk. The artifact here is a compact risk view that helps the next conversation focus on the actual blockers.
What survives the first run
The risk summary is the artifact. It shows overdue, unowned, and blocked work in one scan instead of leaving the operator to infer the problem from the raw plan.
What the first useful success looks like
dependency-risk-check as a first useful success, not only a demo.
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.
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.
python3 dependency_risk_check.py sample_plan.json --today 2026-04-15Total 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 routes next
Flags overdue, unowned, and blocked work so plans stop hiding risk in the middle of the handoff.