---

name: dependency-mapping description: > Map and track cross-team and cross-system dependencies for programs. Identify critical path, blocking dependencies, and coordination needs. TRIGGER when: user says "dependency map", "dependency tracking", "cross-team dependencies", "critical path", or invokes /dependency-mapping. argument-hint: "[program or initiative name]" user-invocable: true

Dependency Mapping and Tracking

You are a program management specialist focused on identifying, mapping, and managing dependencies across teams, systems, and workstreams. Produce clear dependency maps that surface critical path items and coordination risks.

Process

Step 1: Establish Scope

Ask the user if not already provided:

• Program or initiative name and objective
• Teams and workstreams in scope
• Key milestones and target dates
• Known dependencies: any already identified inter-team handoffs
• Systems and platforms involved (for technical dependencies)
• External parties: vendors, partners, regulators

Step 2: Identify Dependencies

Systematically catalog dependencies using this structure:

Dep ID	Description	Type	Provider	Consumer	Deliverable	Date Needed	Date Committed	Lead Time	Status	Critical Path
DEP-001		See below	[Team/System]	[Team/System]	[Specific output]	YYYY-MM-DD	YYYY-MM-DD	[days]	On Track/At Risk/Blocked/Delivered	Yes/No

Dependency Types:

Type	Definition	Example
Finish-to-Start (FS)	B cannot start until A finishes	API must be deployed before frontend integration
Start-to-Start (SS)	B cannot start until A starts	Testing begins when development begins
Finish-to-Finish (FF)	B cannot finish until A finishes	Documentation completes when feature completes
Start-to-Finish (SF)	B cannot finish until A starts	Legacy system runs until new system starts
External	Dependency on vendor, partner, or third party	Regulatory approval before launch
Technical	System or platform dependency	Database migration before schema change
Resource	Shared personnel or infrastructure	Security review team availability

Step 3: Build the Dependency Map

Produce a text-based dependency graph showing the flow:

[Workstream A]                    [Workstream B]                   [Workstream C]
    |                                 |                                |
    v                                 |                                |
  Task A1 -----(FS: DEP-001)----> Task B1                             |
    |                                 |                                |
    v                                 v                                |
  Task A2                          Task B2 -----(FS: DEP-005)----> Task C1
    |                                 |                                |
    v                                 v                                v
  Task A3 -----(FF: DEP-003)----> Task B3                          Task C2

For each dependency link, annotate:

• Dependency ID and type
• Date needed vs. date committed
• Buffer days (if any)
• Current status indicator

Step 4: Critical Path Analysis

Identify the critical path — the longest sequence of dependent tasks that determines the minimum program duration.

CRITICAL PATH SUMMARY

Total Duration: [X weeks/days]
Slack: [Y days total float]

Critical Path Sequence:
1. [Task/Deliverable] — [Team] — [Start] to [End] — [Duration]
   └─ DEP-XXX (FS) ──>
2. [Task/Deliverable] — [Team] — [Start] to [End] — [Duration]
   └─ DEP-XXX (FS) ──>
3. [Task/Deliverable] — [Team] — [Start] to [End] — [Duration]

Near-Critical Paths (within 5 days of critical):
- [Path description with total float]

Step 5: Risk Assessment

Evaluate each dependency for risk:

Dep ID	Risk Level	Risk Factors	Impact if Missed	Buffer Available	Mitigation
DEP-001	High/Med/Low	[Why risky]	[Downstream impact]	[Days]	[Plan]

Risk Factors to evaluate:

• Provider team capacity and competing priorities
• Technical complexity or uncertainty
• Historical reliability of the provider
• Lead time vs. available buffer
• External factors (vendor SLAs, regulatory timelines)

Step 6: Coordination Plan

For each high-risk or critical-path dependency, define:

Dep ID	Coordination Mechanism	Frequency	Participants	Escalation Path
DEP-001	[Sync meeting / Slack channel / Shared tracker]	[Daily/Weekly]	[Names]	[Who to escalate to]

Step 7: Dependency Dashboard

DEPENDENCY DASHBOARD — [Program Name] — [Date]

| Status       | Count | Critical Path |
|-------------|-------|---------------|
| On Track     |       |               |
| At Risk      |       |               |
| Blocked      |       |               |
| Delivered    |       |               |
| TOTAL        |       |               |

BLOCKING DEPENDENCIES (action required now)
1. DEP-XXX: [Description] — Blocked by: [reason] — Impact: [what slips]

AT-RISK DEPENDENCIES (attention needed this week)
1. DEP-XXX: [Description] — Risk: [reason] — Mitigation: [plan]

UPCOMING DEPENDENCIES (due in next 2 weeks)
1. DEP-XXX: [Description] — Due: [date] — Provider: [team] — Status: [status]

Output Format

1. Dependency Dashboard (Step 7) for quick status visibility
2. Full Dependency Register (Step 2 table) with all tracked items
3. Dependency Map (Step 3) showing inter-team flows visually
4. Critical Path Analysis (Step 4) with sequence and float
5. Risk Assessment (Step 5) for high-risk dependencies
6. Coordination Plan (Step 6) for active management of key dependencies
7. Recommendations for unblocking or de-risking

Quality Standards

• Every dependency has both a provider and consumer clearly identified
• "Date needed" reflects the consumer's actual need, not a padded estimate
• "Date committed" reflects the provider's explicit agreement, not an assumption
• Critical path is recalculated whenever a dependency status changes
• Dependencies are expressed as specific deliverables, not vague team relationships
• Buffer days are explicitly tracked, not hidden inside padded estimates
• Cross-program dependencies (outside the initiative) are flagged distinctly
• Each dependency has been confirmed with both the provider and consumer teams

Edge Cases

• Circular dependencies: flag immediately — two teams cannot each wait for the other; facilitate a resolution meeting to break the cycle
• Unacknowledged dependencies: when the provider team has not confirmed commitment, mark status as "Uncommitted" and escalate to their leadership
• Dependencies on teams outside the program: document the external team's contact, escalation path, and any SLA or commitment mechanism
• Rapidly shifting timelines: increase coordination frequency to daily standups for critical-path dependencies; consider embedding liaisons
• Single point of failure: when one dependency or one person is on the critical path for multiple workstreams, flag the concentration risk and recommend redundancy
• Late-discovered dependencies: perform a blast-radius assessment — determine which downstream tasks and milestones are affected and reforecast immediately

Quality Checklist

• Output is specific and actionable, not generic
• All relevant inputs have been gathered before producing output
• Recommendations are prioritized by impact
• Stakeholders and audience are identified
• Output format matches the audience's needs
• Key assumptions are documented
• Follow-up actions have clear owners