dependency-mapping

# Dependency Mapping Skill

Systematic identification and management of cross-project dependencies.

## Purpose

This skill provides a framework for:
- Dependency identification
- Dependency classification
- Impact analysis
- Critical path identification
- Dependency tracking and management

---

## Prerequisites

Before dependency mapping, ensure:

| Prerequisite | Required For | Source |
|--------------|--------------|--------|
| Project schedules | Timeline analysis | Project managers |
| Project deliverables | Dependency identification | Project plans |
| External contracts | Vendor dependencies | Procurement |
| Integration points | Technical dependencies | Architecture |

---

## Dependency Types

### Internal Dependencies

| Type | Definition | Example |
|------|------------|---------|
| **Finish-to-Start (FS)** | B starts when A finishes | Development → Testing |
| **Start-to-Start (SS)** | B starts when A starts | Parallel workstreams |
| **Finish-to-Finish (FF)** | B finishes when A finishes | Code freeze → Doc freeze |
| **Start-to-Finish (SF)** | B finishes when A starts | Rare, shift handoff |

### External Dependencies

| Type | Definition | Risk Level |
|------|------------|------------|
| **Vendor** | Third-party delivery | Medium-High |
| **Regulatory** | Approval or certification | High |
| **Infrastructure** | Environment availability | Medium |
| **Integration** | API or system availability | Medium-High |
| **Resource** | Shared resource availability | Medium |

---

## Dependency Mapping Gates

### Gate 1: Dependency Identification

**Objective:** Identify all dependencies across portfolio

**Actions:**
1. Review project schedules for cross-project links
2. Interview project managers
3. Document deliverable handoffs
4. Identify external dependencies

**Identification Questions:**
- What does this project need from other projects?
- What does this project provide to other projects?
- What external inputs are needed?
- What must be complete befor