How do I install the Dependency Map skill?

Run npx skillmds@latest add nandanosql/dependency-map in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Dependency Map safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Dependency Map?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Dependency Map free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Dependency Map?

nandanosql (@nandanosql) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Dependency Map by nandanosql — Agent Skill

Name: Dependency Map
Author: nandanosql

File contents

Purpose

Visualize and manage cross-team and cross-system dependencies that create execution risk. Identifies blockers, critical paths, and coordination needs so teams can plan around constraints instead of discovering them mid-sprint.

Key Concepts

Dependency Types

Type	Example	Risk Level
Team-to-team	"We need API from Platform team"	High — coordination required
Feature-to-feature	"Login must ship before settings"	Medium — sequencing needed
External	"Waiting on vendor integration"	High — outside your control
Infrastructure	"Needs new database schema"	Medium — technical coordination
Data	"Requires analytics pipeline"	Medium — often underestimated

Application

Step 1: Map Dependencies

## Dependency Map: [Initiative/Quarter]

### Our Deliverables
| # | Deliverable | Team | Depends On | Dependency Type | Status |
|---|-----------|------|-----------|----------------|--------|
| 1 | [Item] | [Us] | [Item from other team] | [Type] | [Clear/At risk/Blocked] |
| 2 | [Item] | [Us] | [Item from other team] | [Type] | [Status] |

### What Others Need From Us
| # | Deliverable | Requesting Team | Due Date | Status |
|---|-----------|----------------|----------|--------|
| 1 | [Item] | [Team] | [Date] | [Status] |

Step 2: Identify Critical Path

**Critical path (longest dependency chain):**
[A] → [B] → [C] → [Final deliverable]

**Total lead time:** [X weeks]
**Bottleneck:** [The dependency that has the least slack]
**Mitigation:** [How to reduce critical path length]

Step 3: Dependency Management Plan

| Dependency | Owner | Check-in Cadence | Escalation Trigger |
|-----------|-------|-----------------|-------------------|
| [Dep 1] | [Name] | [Weekly/biweekly] | [If delayed by >X days] |

Quality Rubric

Dimension	0	1	2
Coverage	Internal only	Internal + 1 external	All dependency types mapped
Ownership	Unowned	Partially owned	Every dependency has an owner
Critical Path	Not identified	Listed but not analyzed	Identified with bottleneck + mitigation
Cadence	One-time map	Updated on request	Regular check-in schedule

References

Related Skills

skills/planning/risk-assessment/SKILL.md — Dependencies create risks
skills/planning/roadmap-planning/SKILL.md — Dependencies affect sequencing
skills/communication/stakeholder-map/SKILL.md — Dependency owners are stakeholders

Skill type: Component Domain: Planning & Prioritization

---name: dependency-mapdescription: Visualize and manage cross-team and cross-system dependencies that create execution risk. Identifies blockers, critical paths, and coordination needs before they become surprises.---## PurposeVisualize and manage **cross-team and cross-system dependencies** that create execution risk. Identifies blockers, critical paths, and coordination needs so teams can plan around constraints instead of discovering them mid-sprint.---## Key Concepts### Dependency Types| Type | Example | Risk Level ||------|---------|-----------|| **Team-to-team** | "We need API from Platform team" | High — coordination required || **Feature-to-feature** | "Login must ship before settings" | Medium — sequencing needed || **External** | "Waiting on vendor integration" | High — outside your control || **Infrastructure** | "Needs new database schema" | Medium — technical coordination || **Data** | "Requires analytics pipeline" | Medium — often underestimated |---## Application### Step 1: Map Dependencies```markdown## Dependency Map: [Initiative/Quarter]### Our Deliverables| # | Deliverable | Team | Depends On | Dependency Type | Status ||---|-----------|------|-----------|----------------|--------|| 1 | [Item] | [Us] | [Item from other team] | [Type] | [Clear/At risk/Blocked] || 2 | [Item] | [Us] | [Item from other team] | [Type] | [Status] |### What Others Need From Us| # | Deliverable | Requesting Team | Due Date | Status ||---|-----------|----------------|----------|--------|| 1 | [Item] | [Team] | [Date] | [Status] |```### Step 2: Identify Critical Path```markdown**Critical path (longest dependency chain):**[A] → [B] → [C] → [Final deliverable]**Total lead time:** [X weeks]**Bottleneck:** [The dependency that has the least slack]**Mitigation:** [How to reduce critical path length]```### Step 3: Dependency Management Plan```markdown| Dependency | Owner | Check-in Cadence | Escalation Trigger ||-----------|-------|-----------------|-------------------|| [Dep 1] | [Name] | [Weekly/biweekly] | [If delayed by >X days] |```---## Quality Rubric| Dimension | 0 | 1 | 2 ||-----------|---|---|---|| **Coverage** | Internal only | Internal + 1 external | All dependency types mapped || **Ownership** | Unowned | Partially owned | Every dependency has an owner || **Critical Path** | Not identified | Listed but not analyzed | Identified with bottleneck + mitigation || **Cadence** | One-time map | Updated on request | Regular check-in schedule |---## References### Related Skills- `skills/planning/risk-assessment/SKILL.md` — Dependencies create risks- `skills/planning/roadmap-planning/SKILL.md` — Dependencies affect sequencing- `skills/communication/stakeholder-map/SKILL.md` — Dependency owners are stakeholders---**Skill type:** Component**Domain:** Planning & Prioritization

Frequently asked questions

Dependency Map