Map project dependencies and critical paths in Claude Code

Use dependency-mapping to show what blocks work, which tasks can proceed, and which chain determines delivery time.

Install in Claude Code

Claude Code and a task list with durations and owners.

Open the pinned GitHub source below and retrieve the `tech-lead/technical-planning/skills/dependency-mapping/` directory from that revision.
Copy it into `.claude/skills/dependency-mapping/` in your project, keeping `SKILL.md` and its companion files together.
Open Claude Code in the project root and enter `/dependency-mapping` followed by the example task.

Example task

Provide an API task of two days, web integration of three, help docs of one, and acceptance of one. Integration waits for the API and acceptance waits for integration. Help docs can proceed independently.

What to check

The graph identifies the six-day API-to-integration-to-acceptance chain and shows docs can run alongside it.

Original SKILL.md on GitHub · Updated 2026-11-11

Frequently asked question

How do I tell whether a dependency blocks work?

Ask whether the downstream task can begin before the other result exists. If it can, record when it needs information.