Dependency & Blocker Radar
Track blockers without blame, escalate with impact, and keep dependency chains visible
Dependencies and blockers are a persistent source of schedule slip, especially when approvals or other teams are required. This recipe creates a dependency register, flags blocked work, and provides a psychologically safe escalation path focused on system constraints, not blame.
INGREDIENTS
PROMPT
Create a skill called "Dependency & Blocker Radar". Input: a plan (milestones/tasks) + any known dependencies. Output: dependency register + blocker summary + escalation drafts. Required behavior: - Track blocker aging and calculate milestone impact. - Provide escalation drafts that avoid blame and focus on impact + decision needed. - If blockers are people-driven, use neutral language and propose system fixes (handoff times, clear SLAs). - Maintain a "blocker history" format for retrospectives. Guardrails: - Never accuse individuals; describe constraints and required actions. - If the dependency is uncertain, log it as a risk with a mitigation plan.
How It Works
Provide your deliverables or milestone plan plus any known dependencies. The recipe builds
a dependency register, identifies what's currently blocked, calculates milestone impact,
and generates escalation messages that frame blockers as system constraints — never personal
accusations.
What You Get
- Dependency register: item, depends on, owner, due date, status, escalation date
- Blocker report: what's blocked, how long, and the downstream milestone impact
- Escalation drafts: neutral language, focused on impact and the decision needed
- Unblock plan: next actions and owners for each blocker
- Blocker history: resolution log for retrospectives
Setup Steps
- Provide your milestone plan or current task list
- List known dependencies (teams, vendors, approvers, artifacts needed)
- Set an escalation threshold (e.g., blocked > 2 days triggers escalation)
- Review the register and send any escalation drafts
Tips
- Auto-escalation thresholds: 1, 2, or 5 days (configurable)
- If a dependency is uncertain, it's logged as a risk with a mitigation plan
- For people-driven blockers, the recipe proposes system fixes (handoff SLAs, clear ownership) rather than naming and shaming
- Dependencies can be tracked at milestone or task level
- Weekly blocker summary pairs well with status reporting recipes